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

Annotations only declare readOnlyHint=true, so the description carries the rest of the load and does it well: it discloses the 6-hour refresh cadence, clarifies that confidence is a label (HIGH/MED) and never a numeric weight, and warns that no methodology or source attribution is included by design. It stops short of describing pagination or error behavior, but the key semantic caveats are surfaced.

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?

Front-loaded with the action, then the return shape, then the caveats; every sentence carries information. The closing sentence about the 'anonymous surface' is slightly meta and verbose, but it still conveys that tiers/families are intentionally withheld.

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, and the description compensates by enumerating the return fields (value, unit, as_of, data_tier, confidence, verify_url, citation_url) and the freshness guarantee. Combined with the confidence-label clarification and the explicit attribution limitation, an agent has enough to call and interpret the result correctly.

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% and the single slug parameter is already fully documented in the schema, including the accepted FLOPS-<MODEL>-OD/-SPOT/-DEPIN and bare gpu_model forms. The description adds no syntax, format, or resolution-order detail beyond that, so the baseline 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?

The description states a specific verb and resource: 'Fetch the current published value for a FLOPS compute price index,' and even lists the returned fields, so the agent knows exactly what the call yields. It does not explicitly distinguish itself from the sibling get_index, so an agent cannot tell from the text alone whether get_index is the fuller/different counterpart.

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 positions itself as the 'cheapest way to answer what is the latest public reference price for X?', which implies usage context. However, it never names an alternative (get_index, search_indices, verify) or states a when-not condition, so routing between this and its siblings is left to inference.

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