Context
Part of #6226 (MCP platform epic). An LLM/agent client selects which MCP tool to call largely based on each tool's registered description text — a vague, jargon-heavy, or ambiguous description leads to wrong tool selection or agents failing to discover a tool that would have solved their task. This is valuable independent of the shared-core (#6227) and chat-interface (#6230) work: better tool descriptions improve every existing MCP consumer today, not just future ones.
Requirements
- Read every registered tool's description across both
packages/loopover-mcp/bin/loopover-mcp.js and src/mcp/server.ts (~150 tools combined).
- Flag any description that: is too short to disambiguate from a similarly-named sibling tool, uses internal jargon a general-purpose agent wouldn't recognize (repo-internal terminology without a one-clause explanation), or doesn't state its required parameters' meaning clearly enough for an agent to construct a valid call without guessing.
- For each flagged tool, propose a concrete, improved description (not just "this is unclear" — write the replacement text).
- Submit the improved descriptions as a batch PR (or split into a few PRs by tool category if the diff is large) — this is a real, shippable fix, not just a research report.
Test Coverage Requirements
No behavior change (descriptions are metadata), but confirm existing tool-registration tests don't hardcode the old description text in a way that would break.
Deliverables
Expected Outcome
Any MCP client (today's agents, and a future chat interface per #6230) selects the right tool more reliably because every description is clear and unambiguous.
Links & Resources
Context
Part of #6226 (MCP platform epic). An LLM/agent client selects which MCP tool to call largely based on each tool's registered description text — a vague, jargon-heavy, or ambiguous description leads to wrong tool selection or agents failing to discover a tool that would have solved their task. This is valuable independent of the shared-core (#6227) and chat-interface (#6230) work: better tool descriptions improve every existing MCP consumer today, not just future ones.
Requirements
packages/loopover-mcp/bin/loopover-mcp.jsandsrc/mcp/server.ts(~150 tools combined).Test Coverage Requirements
No behavior change (descriptions are metadata), but confirm existing tool-registration tests don't hardcode the old description text in a way that would break.
Deliverables
Expected Outcome
Any MCP client (today's agents, and a future chat interface per #6230) selects the right tool more reliably because every description is clear and unambiguous.
Links & Resources
packages/loopover-mcp/bin/loopover-mcp.js,src/mcp/server.ts