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

The readOnlyHint annotation already declares this is a safe read operation. The description adds useful behavior beyond annotations: result ordering is cheapest first, results are capped at 10, and the response includes country, CUDA, disk, network, and price.

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 two tight sentences with no filler. It front-loads what the tool returns and then explains the downstream use of the offer id.

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 simple read-only listing tool with complete schema coverage and no output schema, the description is largely complete. It explains ordering, result cap, returned fields, and how to use the id, though it could mention pagination or empty-result behavior.

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 100%, so the input parameters are already well documented. The description reinforces that gpu selects one GPU model, but it does not add syntax or deeper meaning for count beyond what the enum schema provides.

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 states a specific resource and scope: concrete machines of one GPU model, ordered cheapest first, with an explicit limit of up to 10. It also names the returned attributes and distinguishes the tool from the sibling launch_server by explaining how offer ids are used.

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?

It clearly positions the tool as a selection step before launch_server by saying to use the id as offer_id there. It does not explicitly say when not to use it or contrast it directly with list_gpu_types, but the intended workflow is clear.

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