compare_gpu_prices

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

Annotations only declare readOnly/openWorld, and the description adds substantial behavior beyond that: 'cheapest' is scoped to tracked providers not the whole market, reserved rates are excluded by default and never ranked as cheapest, tier_class taxonomy is enumerated, data_age_hours/degraded/stale thresholds are disclosed, and excluded_too_old is reported.

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?

Front-loads the core action and scope, and nearly every sentence carries operational detail. It is dense and slightly repetitive ('cheapest among tracked providers' restated as reserved 'never reported as cheapest') with awkward mid-sentence line breaks, but nothing is filler.

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?

For a 7-parameter read tool it covers ranking semantics, tier classes, freshness cutoffs and the not_found fallback; return-field explanation is partly redundant given an output schema exists, but it doesn't hurt. The only real omission is the undocumented 'mode' parameter.

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%, so the description must carry all parameter meaning, and it does for gpu (with examples), limit (1-25), on_demand_only, include_reserved, include_history and max_data_age_hours. The 'mode' parameter (default 'full') is never mentioned, leaving one of seven parameters undocumented anywhere.

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?

States a specific verb (compare), resource (tracked GPU rental prices), scope (one model, cheapest first) and gives example model strings. It is distinguishable from deal-oriented siblings like compare_deals and search_deals, though the overlap with get_price_changes (history/price-change data) is never explicitly addressed.

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?

Gives concrete conditions for the optional flags: on_demand_only keeps only on-demand rates, include_reserved pulls in reservation rates that are otherwise dropped, include_history adds history payloads, max_data_age_hours drops stale rates. It also states the unknown-model fallback. It stops short of naming siblings to use instead.

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