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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful context by noting data is read live from the chain and mentions the fee/no-guarantee disclosure, which goes beyond what annotations provide. Minor gap: no mention of potential latency or partial data.

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, tightly packed sentence that front-loads the core purpose ('Read-only snapshot') and then lists all data points. Every word adds value; no fluff, repetition, or unnecessary clauses. It is an excellent example of conciseness while maintaining high information density.

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?

Given the zero-parameter input and the presence of an output schema, the description covers the essential data fields and the disclosure. It doesn't explicitly describe the output schema structure (but the schema exists, so not required per rubric). Minor gap: it doesn't state common use cases or scenarios, but for a read-only snapshot tool, this is nearly complete.

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 and the schema is an empty object, so there is no parameter ambiguity. The description fully compensates by listing all the fields the snapshot includes, giving the agent a clear sense of what the output contains. With no parameters to document, a perfect score is appropriate.

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 states the tool provides a read-only snapshot of the $AI/HYPE AiCurve and enumerates the specific data points (price, sold, retired, etc.). It distinguishes itself from the sibling tools (build tx, quote) by focusing on snapshot data, though it doesn't explicitly name alternatives.

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 implies usage: when a market snapshot is needed, not for building transactions or quotes. The read-only nature and the listed data points make it clear this is for informational retrieval. However, it doesn't explicitly state when not to use it or name alternatives, so it's a step below full guidance.

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