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

Annotations already cover readOnly/openWorld/idempotent/non-destructive, and the description adds genuinely new behavioral facts: the content is 'written ahead of time, not generated' (static, deterministic answers), and it enumerates the exact response shape — plain-English meaning, practical implication, mechanics, a common misconception, and a dated primary source. With no output schema, this disclosure is the main source of that information.

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 core purpose leads, followed by the content list and the input forms, with the key qualifier 'written ahead of time, not generated' at the end. It is dense and the first sentence is long, but nearly every clause carries information an agent needs.

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 one-parameter, no-output-schema tool, the description adequately covers both input variety and return content. The only real gap is the absence of sibling routing guidance (e.g., coin-specific lookups belong to coin_profile).

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% so the baseline is 3, but the description adds concrete accepted-value examples ('impermanent loss', 'what is an NFT', 'proof of work vs proof of stake', 'defi terms') that make the single parameter's expected format clearer than the schema's own one-liner.

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 (explain/define) and resource (crypto, blockchain, trading or crypto-technology terms) and immediately scopes what the answer contains. An agent can distinguish this from coin_profile or explain_transaction without opening any schema.

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?

It clarifies the accepted input shapes (a term, a 'what is' question, 'X vs Y', a topic), which is useful. But it never says when to prefer this over siblings like coin_profile or search, and gives no exclusions, so the routing decision is left implicit.

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