compare_models

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without telling whether the call is synchronous, how results are presented, whether it has side effects (e.g., costs, rate limits), or what happens if a model fails. This is a significant gap for a tool that compares models.

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, direct sentence that starts with the verb 'Compare'. It is concise, front-loaded, and contains no filler words. Every word earns 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?

The tool has modest complexity (2 params, no output schema). The description states the core purpose, but without annotations or an output schema it lacks detail on return values and behavioral context. It is a bare minimum viable description, but not rich enough for an agent to fully anticipate the result.

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 schema already documents both 'prompt' and 'models'. The description adds a minimal semantic hint ('same prompt') but doesn't explain nuances like whether 'models' is an ordered list or how defaults behave. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Compare') and the resource ('responses from different models') along with the context ('same prompt'). However, it doesn't specify what 'compare' means (e.g., side-by-side output, diff, metrics) and there are no sibling tools to differentiate from, so it falls short of a 5.

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 is provided on when to use this tool, preconditions, or alternatives. The description is purely functional and doesn't mention any exclusions or scenarios where another tool would be preferred. Since the schema shows it requires a prompt, but that's structural not usage guidance.

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