compare_prices

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

With no annotations, the description carries the full burden. It discloses concurrent fetching, sorting cheapest first, % delta inclusion, and optional baseline region comparison. This provides solid behavioral detail beyond basic read or write hints.

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 concise and well-structured: a clear purpose sentence, a behavioral note, then listed arguments. Every sentence adds value without redundancy or fluff.

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 presence of an output schema, return value details are not needed. The description covers input parameters, concurrency, sorting, delta, and baseline. It could mention potential limits (e.g., number of regions) or prerequisites, but overall it's sufficiently complete for a comparison tool.

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 the description compensates well. For 'spec', it explains it's a PricingSpec dict like get_price and notes region override. 'regions' is clarified with an example list. 'baseline_region' includes purpose. Meaning is added beyond the basic schema types.

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 'Compare pricing for any service across multiple regions' with a specific verb and resource. It distinguishes itself from siblings like get_price, get_prices_batch, and find_cheapest_region by focusing on cross-region 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?

The description implies usage when you need to compare pricing across regions, but lacks explicit guidance on when to use this tool versus alternatives such as find_cheapest_region or get_prices_batch. No when-not-to-use or exclusion criteria are provided.

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