recommend_mcp_for_task

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses the output structure: 'Returns top 3 ranked picks with reasoning, install commands, and quality scores.' This is sufficient for a read-only recommendation tool. It could mention ranking criteria or data sources for greater transparency, but the current description is clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first states purpose and output, the second gives usage guidance. It is front-loaded with key information and contains no superfluous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema), the description adequately covers what the tool does and returns. It mentions the top 3 picks, reasoning, install commands, and quality scores. It could be enhanced by referencing sibling tools for alternative uses, but it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with a description for the 'task' parameter. The tool description does not add additional examples or constraints beyond the schema's example. Thus, per the baseline, a score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Recommend the best MCP servers for a natural-language task.' It specifies the verb (recommend), resource (MCP servers), and context (natural-language task). This distinguishes it from sibling tools like search_mcp_servers (which lists servers) and assess_server (which evaluates a single server).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the tool: 'Use this when the user asks for the right MCP server for a task they want to do.' It lacks explicit when-not-to-use or alternatives, but the context is clear enough for most agents.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.