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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral note ('Preserve returned URLs exactly'), which signals output-handling expectations, but nothing about scope limits beyond 'public' or failure behavior when a slug is unknown.

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 compact sentences with zero filler; the core purpose is front-loaded and the URL-preservation instruction follows, each earning its place.

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 one-parameter lookup with an output schema and full annotation coverage, the description is nearly sufficient. It clarifies the lookup is limited to public data and how to handle returned URLs, though it says nothing about behavior for invalid or missing slugs.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that the slug is the identifier returned by search_mcps. The description adds no format, case-sensitivity, or validation detail beyond that baseline, so this stays at the standard 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 states a specific verb and resource ('Get public details for one MCP server') scoped by slug, so an agent knows exactly what it retrieves. It does not differentiate itself from the many parallel get_* siblings (get_tool, get_model, get_repository), relying on the noun to do the routing work.

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?

Usage is only implied: the schema notes the slug comes from search_mcps, which hints at a search-then-fetch flow, but the description never says when to call this versus search_mcps or other get_* tools. No explicit when/when-not guidance is present.

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