Get AIOrouter Pricing

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

With readOnlyHint:true, the annotation already signals a safe read operation. The description adds useful context beyond that: the pricing is 'public' (implying no special auth required) and denominated in USD per 1M tokens. This helps the agent understand the nature of the data returned, going beyond a simple read-only hint.

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 one concise sentence that front-loads the core purpose (getting pricing) and includes key qualifiers (public, USD per 1M tokens). Every word adds value, with no redundant or filler content.

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?

Given the tool's simplicity (one optional parameter, no output schema, read-only annotation), the description is largely complete. It clearly states what the tool returns (pricing in a specific unit) but does not specify whether omitting 'model' returns all models or exactly how the result is structured. This minor gap prevents a perfect score.

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?

The input schema already provides a complete description for the only parameter ('model' as an optional string). Since schema coverage is 100%, the baseline is 3. The tool description does not add any additional meaning about the parameter, so it neither enhances nor detracts from the 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 clearly states the tool's function: to get public retail pricing for AIOrouter models, with specific unit (USD per 1M tokens). This distinguishes it from sibling tools like aiorouter_estimate_cost or aiorouter_list_models, making the purpose unambiguous.

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 implies when to use this tool (when needing list prices) but does not explicitly mention alternatives or situations where another tool would be more appropriate, such as aiorouter_estimate_cost for custom cost calculations. There are no exclusions or prerequisites, so it relies on the agent inferring the usage context.

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