get_pricing

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

With no annotations, description carries burden and adds behavioral context: filter combination logic and empty list return for unknown pairs. Does not cover rate limits or auth, but provides key behavioral trait.

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?

Two sentences, front-loaded with purpose, followed by behavioral detail. No wasted words, efficient structure.

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 an output schema exists, description explains key return behavior (empty list). Could mention output schema fields briefly, but is complete enough for selection. Slightly more detail on output would improve.

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 0%, so description must compensate. It explains parameters as filters (model, provider) and their optionality, but lacks individual parameter details like format. Adequate but not thorough.

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?

Description clearly states 'Return current pricing for one model, one provider, or all models,' specifying the verb (return) and resource (pricing), and distinguishes from sibling tools that handle providers, comparisons, etc.

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?

Explains that both filters are optional and AND-combined, and describes behavior for unknown (provider, model) returning empty list, which guides usage. Could explicitly state when to use vs alternatives, but sibling differentiation is clear from purpose.

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