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

With no annotations provided, the description carries the full behavioral disclosure burden. It communicates that the data is live and enumerates the output dimensions, and the word 'snapshot' implies a read-only operation. It does not define how 'freshness/health' is computed or specify the exact response structure, but it is reasonably transparent for a zero-parameter stats tool.

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 a single front-loaded sentence that moves from the core concept ('Live market snapshot') to a scannable colon-separated list of output fields. Every term earns its place and there is no filler or redundant wording.

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 zero-parameter, read-only market snapshot with no output schema, the description covers the essential return values an agent needs to decide whether to call it and how to use the result. It could be slightly more explicit about the return format or units, but nothing critical is missing for selecting and invoking the 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 tool has zero parameters, so the input schema is already complete and no parameter documentation is needed. The description does not add parameter-level meaning, but that is unnecessary here; the baseline of 4 applies because there is nothing for the description to compensate for.

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 clearly identifies the tool as a live market snapshot and enumerates the specific metrics it provides (total offers, GPU models, idle-capacity share, per-provider freshness/health, cheapest price per model, fee_bps). This distinguishes it from sibling tools like get_offer or search_offers, though it lacks an explicit action verb and does not name any sibling directly.

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 'live market snapshot' implies this is the right tool for a high-level overview of current market conditions rather than for specific offer searches or historical analysis. However, there is no explicit guidance about when to use this tool instead of related siblings such as best_value, spot_spread, or provider_reliability.

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