compare_mcp_servers

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that results include install commands, evidence, health, GitHub stars, last commit and quality score, but says nothing about behavior with invalid or unregistered IDs, partial data, or result ordering.

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?

A single front-loaded sentence that leads with the action and cardinality, then lists the compared attributes. No filler, no redundancy.

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 enumerated field list usefully tells the agent what it will receive. What is missing is how to obtain valid server IDs and what happens on partial or unknown inputs, which matters because ids are required.

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% and the single parameter 'ids' is documented there, including minItems 2 and maxItems 4. The description's '2 to 4 MCP servers' merely restates that constraint rather than adding format or sourcing guidance, so the baseline 3 applies.

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 (compare) and resource (MCP servers) with an explicit cardinality constraint of 2 to 4, and enumerates the dimensions compared. It does not, however, explicitly differentiate itself from sibling get_mcp_alternatives, which an agent might reasonably confuse with a comparison tool.

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?

There is no statement of when to reach for this tool versus get_mcp_alternatives, recommend_mcp_stack, or search_mcp_servers, nor any prerequisite about where valid server IDs come from. Usage is only weakly implied by the name and the field list.

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