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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false, destructiveHint=false), so the bar is lower. The description adds genuine non-obvious behavior: the ranking order, that client preference is evidence rather than a compatibility test, and that requirement filtering does not happen here. These are real disclosures beyond the structured fields.

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?

Four tight sentences, front-loaded with the purpose, and each subsequent sentence adds a distinct behavioral constraint rather than filler. No bloat, though the terseness borders on cryptic in places ('must be checked upstream').

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?

For a read-only recommendation tool whose annotations already declare the safety profile and with no output schema, the description covers ranking behavior and the key limitation (no requirement filtering). It is nearly complete, though return shape and pagination via 'limit' are unspecified.

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 coverage is 0%, so the description carries the full burden. It adds meaning for 'client' (a preference treated as evidence, not tested compatibility) and contextually for 'task', but 'type' (the enum of skill/mcp/plugin/agent/prompt/rule) and 'limit' are completely unexplained in both schema and description.

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?

States a specific action and output: 'Find a shortlist for a task.' The verb/resource combination (recommend/find a shortlist) is clear and distinguishable from search_resources and get_resource by implication, but it never names those siblings, so differentiation is left to inference rather than stated.

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?

It implies the tool ranks rather than filters ('keyword relevance precedes repository stars') and warns that hard requirements must be 'checked upstream', which quietly signals its scope boundary. However, it never explicitly says when to pick this over search_resources or get_resource, so the agent must infer the routing.

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