Compare models

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

No annotations provided, so description should disclose behaviors. It states 'Offline' but does not clarify what that entails (e.g., no network call, local cache). No mention of permissions, side effects, or data sources. The sorting and ratio calculation are mentioned but minimal.

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?

One sentence covering key aspects: comparison, sorting, ratio, offline. It is efficient but could be more structured (e.g., bullet points). No unnecessary words.

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 output schema present, return values are covered. However, ambiguity about 'Offline' and lack of explanation for 'multiple of the cheapest' leaves gaps. Adequate for a simple comparison tool but not fully comprehensive.

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%, so all parameters are documented. The description adds limited value beyond schema: 'fixed token shape' reinforces input/output tokens, but no extra formatting or constraints.

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 tool compares models side by side for a fixed token shape, sorts cheapest first, and includes the multiple of the cheapest. It mentions 'offline' and distinguishes from sibling tools like estimate_cost and get_pricing by focusing on comparison.

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 explicit guidance on when to use this tool vs siblings such as select_optimal_model or estimate_cost. The description implies usage for fixed token shapes and offline computation, but does not specify prerequisites or exclude alternatives.

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