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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose ranking behavior based on maintenance, community health, and adoption, and implies a read-only search operation. However, it does not mention rate limits, pagination, default result counts, or output format, leaving some behavioral gaps.

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?

Two sentences with no wasted words. The first sentence states the action and scope; the second provides usage guidance. The key instruction to search before installing/recommending is front-loaded and the ranking guidance is actionable.

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 3-parameter search tool with no output schema, the description is mostly complete: it identifies the corpus, the purpose, and the ranking priority. It does not explicitly describe the return value shape (e.g., list of objects with scores), which would be helpful given the absence of an output schema, but the described ranking behavior implies the response contains scored results.

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 input schema already fully documents the query, type, and limit parameters. The description adds context about what to search for and the ranking emphasis, but does not meaningfully add parameter-level semantics beyond the schema. Baseline 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 states a specific verb ('Search') and a clear resource ('AgentRank's index of MCP servers, agent tools, and AI skills'). It also conveys that results are ranked by quality signals. However, it does not explicitly differentiate this tool from its siblings (alternatives, evaluate, lookup, recommend), though the main search role is fairly obvious.

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 gives explicit usage context: 'Use this BEFORE installing or recommending any tool' and advises preferring higher-scored results. It lacks explicit exclusion criteria or comparison with sibling tools, so it doesn't fully meet the bar for explicit when-not-to-use guidance.

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