Compare Models

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal the output contract (explicit discrete states, including unsupported and unknown), which is useful, but it says nothing about whether the tool has side effects, calls external services such as live pricing, requires auth, or how unsupported/unknown are determined.

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 single-sentence description is tightly written, front-loads the key result (explicit comparison states), and has no filler. It is concise but under-specified; the short length is appropriate, yet the one sentence cannot carry the full guidance burden.

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 having an output schema, the tool still lacks essential context: 7 parameters with 0% schema documentation, no annotations, and no description of how source/target/endpoint/platform/pricing combine. An agent cannot confidently construct a correct call from the available text alone.

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 0%, so the description needed to explain what source/target mean and how endpoint/platform/pricing parameters affect the comparison; it does none of that. The property names are somewhat self-explanatory, but the text adds no semantic value beyond the raw schema.

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 uses a specific verb ('Return') and names the explicit output states (same/different/unsupported/unknown), so an agent can tell this is a discrete-state comparison tool rather than a free-form diff. It does not literally state that source and target are models, but the title and sibling context make that reasonably clear. It stops short of 5 because compare_outputs could be confused without more explicit object-of-comparison wording.

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 guidance about when to choose this tool over compare_outputs, resolve_model, or the other comparison/migration siblings, and no mention of prerequisites or exclusions. The description only states what the tool returns, leaving the agent to infer when it is appropriate.

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