get_price

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

With no annotations provided, the description carries the full burden. It discloses important behavioral traits: values are 'delayed and indicative' and the envelope is returned 'as-is.' This goes beyond a simple fetch description, though it does not cover error handling or rate limits. The key user-relevant caveats are addressed, so it earns a 4.

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 three sentences, each with a distinct purpose: stating the action, enumerating the return envelope, and pointing to the alternative. No filler or redundancy; information is front-loaded and efficiently structured.

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?

Despite lacking an output schema, the description explicitly lists the 14 fields returned, which fully covers the return structure. It also adds context about data freshness (delayed, indicative) and directs to get_index for a lighter payload. For a simple one-parameter fetch tool, this is complete enough.

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 schema already provides 100% coverage of the single 'slug' parameter with a clear description and examples. The description does not add additional parameter semantics beyond what the schema offers. Per the rubric, baseline 3 is appropriate when schema coverage is high and the description adds little.

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 'Fetch the current published value for a FLOPS compute price index' with a specific verb and resource. It distinguishes itself from the sibling get_index by clarifying that get_price returns the full envelope while get_index returns a reduced, citation-only payload. This makes the purpose unmistakable.

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 description explicitly directs the user to an alternative: 'Use get_index for the reduced, citation-only payload.' This establishes when to use get_price (when the full 14-field envelope is needed) versus get_index, providing clear usage context.

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