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

No annotations are provided, so the description carries the full burden of disclosure. It transparently explains authentication and payment requirements (Bearer token or per-call fee) and the scope of the request (all nine chains or a single chain). However, it does not describe what happens without valid payment, error behavior, or the response format, leaving gaps for a tool with zero annotation support.

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 long sentence that leads with payment requirements rather than the core purpose, which reduces front-loading effectiveness. The payment details are extensive and somewhat verbose, though they do convey necessary authentication context. It could be restructured to state the function first and move payment details to a secondary position.

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 low complexity (one optional parameter, output schema present), the description covers the essential aspects: what it does (live prices), how to invoke it (omit chain for all), and important constraints (authentication/payment). It does not explain the return value structure, but the output schema presumably handles that. It lacks rate limits or failure scenarios, which would make it more complete, but for a simple price check tool this is adequate.

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 has 0% description coverage, but the description explicitly explains the key behavior of the only parameter: 'Omit chain for all nine.' This directly tells the agent how to use the optional chain field and what the default behavior is. While it doesn't list each enum value (the schema already does), it adds meaningful usage semantics beyond the raw schema.

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's function: 'Live price for every chain in one call' and 'the one cent market check,' which conveys it returns current prices for blockchain networks. It does not use a direct verb like 'get' or 'retrieve,' and it does not explicitly distinguish itself from sibling tools such as market_state, so it misses the top score.

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 as a quick, low-cost market check and provides a concrete instruction: 'Omit chain for all nine.' However, it does not specify when to use this tool versus alternatives like market_state or deep_report, nor does it mention any situations where this tool should be avoided. No exclusions or comparisons are provided.

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