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

Annotations already establish this is a safe read (readOnlyHint=true, openWorldHint=false). Beyond that, the description discloses the temporal scope (this week plus the last eight weeks), the aggregation basis (median listed on-demand), and that base-100 index values and source receipts are included - meaningful return-shape context given no output schema exists.

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?

A single front-loaded sentence that leads with the resource name and layers in the key scoping details. No filler, though 'with the receipts' is a slightly vague tail that could be tightened.

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?

With no parameters, no output schema, and annotations covering the safety profile, the description carries the burden of explaining return content - and it does: metric, aggregation, time window, index, and sources. The only real gap is routing guidance relative to sibling price tools, which is a usage concern more than completeness.

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 takes zero parameters, so there is nothing to document and the schema cannot be a source of ambiguity. Baseline of 4 applies; the description correctly implies no inputs are needed.

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 names a specific resource (the weekly Cloud GPU Price Index) and defines its contents precisely: median listed on-demand H100 SXM rate across providers, plus a base-100 index. An agent knows exactly what data this returns, though it never distinguishes this tool from siblings like gpu_prices or recent_price_changes that likely offer overlapping price data.

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?

There is no statement of when to use this tool versus the four siblings (gpu_prices, list_gpus, provider_prices, recent_price_changes). The weekly-index framing hints at trend analysis, but the agent must infer whether to call this or a sibling for a given price question; no alternatives or exclusions are named.

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