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

No annotations are provided, so the description must carry the transparency burden. It states the tool returns 'metadata + README,' which gives some insight into the return content. However, it does not disclose potential errors (e.g., invalid slug), side effects (none expected), or any special behavior (e.g., caching, rate limits). The description is minimal but not misleading.

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 a single, concise sentence that packs the essential information: what it fetches, the scope (single server), and the identifier type (slug). No filler or redundant wording.

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 simple single-parameter fetch tool, the description covers the key inputs and outputs. It specifies the return includes metadata and README, and an output schema exists to provide formal structure. There are no complex side effects or prerequisites to document. The description is complete for this tool's complexity.

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 for the single 'slug' parameter, which is described as 'server slug (required)'. The description also mentions 'by its slug,' reinforcing this. Since the schema already fully documents the parameter, the description adds marginal value, aligning with the baseline of 3.

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 uses a specific verb ('Get') and resource ('full details (metadata + README) of a single MCP server') with a clear targeting mechanism ('by its slug'). It clearly distinguishes from sibling tools like list_categories, search_servers, and compare_servers, which serve different purposes.

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 implies when to use this tool: when you need full details for a single server and know its slug. However, it does not explicitly mention alternatives or exclusions, such as 'use search_servers if you don't have a slug' or 'use compare_servers for multiple servers.' This is adequate but lacks explicit guidance.

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