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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: results come from real tools/list data rather than marketing copy, so a match implies the capability actually exists. It doesn't discuss rate limits, coverage gaps, or failure modes, so not a 5.

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?

Front-loaded with the core purpose, then usage triggers, then query guidance, so an agent can stop reading early if it only needs the first sentence. The three inline example phrasings are useful but make the middle dense; a slightly tighter example set would read better.

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?

An output schema exists, so return-value detail isn't required, and the annotations carry the safety profile. The description still covers the essentials an agent needs: what it searches, when to invoke it, and how to phrase the query.

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 100%, so baseline is 3, but the description adds real meaning by prescribing query phrasing in plain capability words ('send transactional email', 'query postgres') rather than product names. It also notes that results list matching tools, though it says nothing about the limit parameter beyond the schema.

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 states a specific verb and resource ('Find an MCP server or AI tool that can do a job') and scopes the domain to MCP servers/integrations, which clearly separates it from product-oriented siblings like search_products, compare_products and find_alternatives. An agent can route to it without opening the schema.

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 gives explicit trigger conditions with concrete user phrasings ('is there an MCP for Stripe?', 'something that can scrape websites'), which is strong positive guidance. It does not name a when-not case or point to a specific alternative sibling (e.g. find_alternatives) for adjacent needs, so it stops short of a 5.

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