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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds meaningful context beyond that: the tool returns normalized model names, quote aggregation metrics, observation time windows, and hyperscaler spot mappings. No contradiction with annotations exists.

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 compact and dense, with the core purpose front-loaded and the field list following in one sentence. The standalone 'Free.' is slightly abrupt but not wasteful; every sentence contributes useful information.

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?

With no output schema, the description carries the burden of describing return contents, and it does so thoroughly: model names, provider counts, quote counts, snapshot range, lowest price, and spot mappings. It does not mention ordering or pagination, but with zero parameters that is a minor gap for a read-only reference 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?

The input schema has zero parameters, so the baseline is 4. The description's mention of normalized model names and 'use verbatim as `gpu`' adds useful downstream context even though there is no schema parameter to document.

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 identifies the resource (GPU models) and the exact contents: rental quotes, provider counts, snapshot dates, lowest USD per GPU-hour, and hyperscaler spot mappings. It lacks an explicit verb like 'list' or 'get', but the scope is clear and distinguishable from sibling quote/history tools.

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?

There is no explicit statement about when to use this tool versus siblings like gpu_quotes or gpu_snapshot. The note 'use verbatim as `gpu`' is a downstream usage hint rather than a when-to-use guideline, and no alternatives or exclusions are mentioned.

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