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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: the default to 'current reviewed prices', the caveat that offers 'may still have unsupported billing modes', and the explicit limitation that it does not recommend model capabilities. These are substantive behavioral disclosures.

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?

Three short sentences, each earning its place: the core purpose is front-loaded, followed by default behavior and an important caveat/scope limitation. There is no filler or redundant restatement of schema or annotations.

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 an output schema present and strong annotations, the description does not need to explain return values or safety. However, it omits operational details such as pagination semantics for cursor/limit and the meaning of query, which are relevant for correct invocation. The caveats about billing modes and capability recommendations add context, but the parameter handling gaps keep it from being fully complete.

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%, and the description provides no information about any of the six parameters. It does not explain how limit, query, cursor, status, provider_id, or pricing_tier should be used. The schema property names and the enum/default values provide some self-evident meaning, but the description fails to compensate for the complete lack of schema descriptions.

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 starts with a specific verb+resource: 'Find exact pricing offers and their IDs.' It clearly states the tool's output focus (pricing offers and IDs), and the closing 'No model capability recommendation' distinguishes it from capability-oriented tools. However, it does not explicitly name or contrast the sibling tools, so differentiation remains implicit.

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?

The description provides no guidance on when to use this tool versus siblings like calculate_cost, compare_model_costs, or get_model_pricing. It notes the default status and billing-mode caveat, but these are behavioral facts rather than routing instructions. There are no explicit when-to-use or when-not-to-use statements.

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