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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the bar is lower. The description adds real value beyond them: data is 'read live from chain', no argument is required, and the response includes a fee/no-guarantee disclosure. It doesn't cover rate limits or freshness/staleness semantics.

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 purpose and constraints, no filler. The long enumeration of fields leans on the output schema, but each item aids scanning and the routing sentence is well placed.

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-argument read tool with an output schema and full annotation coverage, this is nearly complete. The only minor gap is not clarifying its relationship to the tx-building siblings.

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?

Zero parameters, which is the baseline-4 case. The description reinforces this explicitly ('Takes no amount'), so an agent won't go looking for parameters.

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+resource ('Read-only snapshot of the $AI/HYPE AiCurve') and enumerates exactly what the snapshot contains. It also differentiates itself from ai_quote_buy/ai_quote_sell by noting those are for a price on a specific amount.

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?

Gives clear context: no amount is taken, and points to ai_quote_buy (flagged as 'the recommended first call') or ai_quote_sell when a price for a specific amount is needed. It does not address ai_build_buy_tx/ai_build_sell_tx, leaving the sibling routing partly incomplete.

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