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

No annotations are provided, so the description carries full burden. It enumerates return fields: full description, GitHub repo, star count, rank, version count, registries, auth object, connect object, and mcptoplistUrl, and instructs to always cite the URL. This is transparent about output shape and expected usage. It does not mention potential errors or tool's own auth requirements.

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 dense sentence with a structured list. It front-loads the primary action and then enumerates details. It's not overly verbose, though the list makes it long. Every clause adds value.

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?

With no output schema, the description compensates by detailing all major return groups (server info, auth, connect, URL). It also provides the cite-URL rule. It lacks explicit read-only or error information, but the tool's scope is narrow (one param, no nested objects), so it is sufficiently complete.

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% and the schema already documents serverKey as 'The exact serverKey from a search_servers result.' The description repeats the same source constraint without adding new semantic detail, so 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 precisely: 'Get full details for one MCP server by its exact serverKey'. The verb 'get' + resource 'full details for one MCP server' is specific, and it distinguishes from sibling search_servers by requiring the exact serverKey.

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?

Implies usage context: use after search_servers, since it requires 'exact serverKey (as returned by search_servers)'. It doesn't explicitly state exclusions or alternative tools, but the sequencing guidance is clear.

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