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 describes the output (scored servers with reason codes) and implies it is a read-only operation (recommendations). While it does not explicitly state side effects or authentication needs, the behavioral transparency is high for a recommendation tool.

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 defines the tool's purpose and output, the second provides explicit usage guidance. It is front-loaded, efficient, and contains no fluff.

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 there is no output schema and no annotations, the description covers the main purpose, output structure (ranking with reason codes), and usage context. It lacks details on default parameter behavior but the schema covers defaults. Overall fairly 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?

Schema description coverage is 100%, so the baseline is 3. The description mentions the 'task or capability query' but does not add additional meaning beyond the schema. No further parameter semantics are provided.

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 starts with a specific verb-resource pair ('Get ranked MCP server recommendations') and explicitly distinguishes itself from the sibling `query_registry` by contrasting 'opinionated ranked list' with 'filtered search'. This makes the tool's purpose very clear.

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 clearly states when to use this tool ('when you want an opinionated ranked list') and explicitly names the alternative (`query_registry`). However, it does not mention the other siblings (`get_server`, `report_server`), so it is not exhaustive but still clear for the most similar tool.

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