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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: the data is collected rather than live, and each page costs one data unit — a quota/cost disclosure an agent would otherwise miss. It does not explain the non-idempotent pagination behavior implied by idempotentHint=false.

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 dense sentences, no filler: returned fields first, then the data-freshness caveat, then pagination and cost. Front-loaded and every sentence carries information an agent needs.

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?

There is no output schema, so the description compensates by enumerating the returned columns. Combined with pagination defaults, per-page cost, and the non-live-data caveat, nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the schema documents gpu, page.limit, page.cursor, and count. The description still adds unit semantics absent from the schema — prices are USD per whole node hour, and node size is controlled via count — which is more than restating field docs.

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 ('List every provider offer for one GPU model and node size') and enumerates the returned fields (provider, instance type, region, GPU count, on-demand/spot price, links, last update). It is distinguishable from get_price_history and get_market_snapshot by its per-model offer scope, though it never names those siblings to make the boundary explicit.

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?

Usage is only implied: 'Prices reflect collected data, not a live capacity guarantee' hints that capacity questions belong to get_availability, but no explicit when-to-use or when-not-to-use rule is given. An agent facing get_price_history, get_market_snapshot, and get_availability must infer which tool answers which question.

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