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

Goes well beyond annotations by disclosing the paid x402 mechanism, exact price, error/no-charge behavior for missing/stale data or unknown symbols, and that the response includes payment requirements and a URL. Annotations only cover read-only/idempotent safety, so this extra operational context is valuable.

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-loads the core purpose and follows with usage, error behavior, and payment details. It is dense but nearly every sentence adds operational value, though the pricing is repeated from the title and the sample URL is incidental.

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 output schema, the description compensates by explaining the ranked-table result, the single-coin variant, x402 payment requirements, and error/no-charge conditions. Nothing an agent needs to invoke it correctly appears to be missing.

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 optional symbol parameter is already documented with pattern and examples. The description restates that an optional symbol returns one coin, which is mildly useful but largely duplicates the schema baseline.

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 (per-coin headline mention volume vs 7-day average from the latest 12h tagger run) and specifies the ranked-table shape. It explicitly distinguishes itself from get_sentiment, so an agent can separate the two without opening schemas.

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?

Clearly explains the optional symbol path versus the full ranked table, and explicitly says 'Volume signal, not tone (use get_sentiment for bullish/bearish).' This names the alternative and the condition that selects it.

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