list_gpus

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

With no annotations, the description carries the burden of explaining behavior, and it does so by specifying the output is a current snapshot with total supply, available count, and percentile pricing per GPU model. The verb 'Show' and the aggregate fields make the read-only nature clear, though it does not mention pagination, ordering, or how filter defaults affect 'all'.

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?

One dense sentence front-loads the action and resource before enumerating exactly what the response contains, with no filler or repetition of schema details. Every phrase earns its place.

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?

Despite lacking an output schema, the description enumerates the essential return fields and the input schema covers both filters and defaults. It is slightly incomplete by not acknowledging the optional filters or stating any pagination/limits expectations, but this is a minor gap for a simple snapshot 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 100% description coverage for both optional parameters, so the baseline is 3; the description adds no specific parameter details. It contributes no additional semantic meaning beyond the schema, but none is strictly needed.

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 action ('Show the current snapshot') and resource ('all available GPUs on Vast.ai') with explicit output details: total supply, available count, and percentile pricing. This clearly distinguishes it from sibling search_offers, which implies offer-level searching rather than an aggregate market snapshot.

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 phrase 'current snapshot' implies this is for a high-level market overview, and the sibling list includes search_offers for more detailed searching, so the intended niche is weakly indicated. However, the description never explicitly states when to use this tool over search_offers or what it should not be used for, leaving routing to inference.

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