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

Since no annotations are provided, the description carries the full transparency burden. It discloses the required bearer-token API key, pay-per-call alternatives, the inclusion of bitcoin-specific mempool data, and the behavior that failed sections are listed under 'unavailable'.

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 compact and information-dense: credentials and payment, response contents, then failure behavior. However, the detailed auth and payment attention leads the description, delaying the clearer central purpose announcement.

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 tool with a single enum parameter and an output schema, the description is well covered: it explains auth, cost, the aggregate chain-brief concept, and failure reporting. The main gap is the absence of explicit guidance for when to prefer this over a sibling specialized tool.

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 description coverage is 0%, but the description adds a key parameter nuance: for bitcoin, the response includes the mempool, while other chains rely on the general listed sections. The 'one chain' phrasing also clarifies that exactly one chain is processed per call.

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 states the tool's scope: 'One chain, the whole read in one answer' and lists the specific market analysis sections included. This differentiates it from the many specialized sibling tools, even though it doesn't explicitly name them.

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?

'One chain, the whole read in one answer' implies the tool should be used when an agent wants a single comprehensive chain report rather than a specific metric. However, there are no explicit conditions, exclusions, or comparisons to the specialized sibling tools.

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