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

No annotations are provided, so the description carries the burden. It implies a read operation ('fetch') and that the slug should come from search_servers, but it does not disclose error behavior (e.g., not found), authentication needs, rate limits, or response structure. For a fetch tool this is a notable gap, though the non-destructive nature is implicit.

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 filler; the core purpose is front-loaded, and the next-step hint is a helpful addition without excess.

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?

The description covers the full workflow: where the slug comes from, what the tool does, and what to do next. It does not describe the return value format or error handling, but for a single-parameter read tool with no output schema, the provided context is largely sufficient.

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 the slug parameter is fully described in the schema. The description adds the context that the slug comes from search_servers and gives an example ('owner/repo'), but this is usage guidance rather than new semantics. 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?

States a specific verb ('fetch'), resource ('full mcpnav record for one server'), and how to identify it (slug from search_servers). It also differentiates from siblings by pointing to get_connect_config as the next step and search_servers as the source of the slug.

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?

Explicitly tells the agent to use this after search_servers (slug comes from its results) and to call get_connect_config next for an install snippet. This establishes the intended sequence and distinguishes from the alternative. It doesn't explicitly mention when not to use it, but the context covers the main alternatives.

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