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

With readOnlyHint already declaring a safe read, the description still adds real behavioral context: rows with unknown units/scope/count are silently excluded by numeric filters, billing matching is a case-insensitive substring, and availability is a recorded snapshot rather than live. These are non-obvious semantics an agent cannot infer from the schema or annotations.

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 compact sentences, with the core purpose front-loaded and each following clause carrying a distinct, non-redundant constraint. No filler and nothing repeated from the structured fields.

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?

An output schema exists, so return values needn't be explained, but a 13-parameter tool with zero schema coverage needs far more parameter-level guidance than is given. Several filters (sort, paging, source_backed_only, the VRAM/price variants) remain uninterpretable without trial and error.

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 the load, and it only clarifies billing_model matching and the strictness of numeric filters. It says nothing about sort (including the '-' prefix convention), limit/offset paging, source_backed_only's default of true, or how min_vram_total differs from min_vram_per_gpu and the two max price fields.

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 first clause gives a specific verb and resource ('Find recorded offers') plus the filtering domain ('bounded price/count/VRAM filters'), which is enough to distinguish it from list_price_history or list_providers. It stops short of naming a sibling tool or stating a negative boundary, so it lands just below a 5.

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?

'Availability is recorded, not live' implicitly steers agents away from expecting real-time data, and 'unknown units... never pass numeric filters' warns that numeric filters are strict. However, it never states when to pick this over list_price_history or per-accelerator lookups, leaving the choice to inference.

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