compare_servers

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

With no annotations, the description carries full burden. It only states 'compare', implying a read operation, but doesn't disclose specific behavioral traits like whether it's read-only, permission requirements, or what aspects are compared (e.g., features, ratings).

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?

Single sentence of 7 words is very concise. However, it could include minimal extra context without being verbose. The efficiency is high but slightly under-informative.

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?

Despite an output schema existing, the description omits what 'side-by-side comparison' entails (e.g., which properties are compared, how results are presented). This leaves the agent without enough context to evaluate when this tool is useful.

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 input schema already documents slugA and slugB. The description adds no further meaning (e.g., how to obtain slugs or what constitutes a valid server slug). 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?

The description 'Compare two MCP servers side-by-side' clearly states the verb and resource. It distinguishes from siblings like 'get_server' (single server) and 'search_servers' by focusing on comparison, though it doesn't explicitly name alternatives.

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?

No guidance on when or when not to use this tool. It does not explain scenarios where a single server or search might be more appropriate, nor does it mention prerequisites or alternatives.

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