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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety and open-world reach are covered. The description adds the default sort behavior ('cheapest matches first unless order says otherwise'), though that default is also stated in the schema's order parameter, and it says nothing about pagination, rate limits, or result freshness beyond 'live prices'.

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 short sentences, zero filler, with the core purpose front-loaded and the ordering caveat and chaining hint following immediately. Nothing is repeated or padded.

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 an 11-parameter, no-required search with a fully documented schema, the definition covers purpose, ordering, and the downstream handoff to create_instance. With no output schema, it could say more about what a result row actually contains (price fields, region, GPU spec), which is the only notable gap.

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 all 11 parameters (including defaults for limit and order) are documented in the schema itself. The description contributes no filter syntax, unit, or format detail beyond what the schema already gives, so the baseline of 3 applies.

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 and resource ('Search rentable GPU servers (offers) with live prices'), and the parenthetical resolves the term 'offers' used elsewhere. It is clearly separable from siblings get_offer (single offer) and list_gpu_models (catalog lookup).

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?

Says when the results are useful ('Each result has an offer id for create_instance'), which routes the agent into the correct next step. It does not explain when to prefer get_offer over this search or list any exclusions, so it stops short of explicit alternatives guidance.

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