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

With no annotations, the description carries the full burden, and it discloses important behaviors: authentication via ChainHelix API key bearer token, an alternative payment method via Binance/x402, and the default behavior of omitting chain to return all nine chains. It does not mention rate limits or pagination, but these are less critical given the read-only report nature and the presence of an output schema.

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 two sentences, but the first sentence dedicates significant length to payment details before the core purpose is stated. This buries the main value proposition behind less essential context, though all included information is relevant. A more front-loaded structure would improve readability.

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 single-optional-parameter tool with an output schema, the description covers the essential operational facts: authentication/payment, default behavior, and what the response contains. It lacks explicit guidance on when not to use it, but the overall completeness for a report-generation tool is solid.

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 0%, so the description must add meaning to the sole 'chain' parameter. The phrase 'Omit chain for all nine' clarifies the default behavior and this is the key semantic nuance beyond the enum. The parameter's enum values are self-explanatory, so additional elaboration is unnecessary.

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 purpose: delivering a 'full market picture in one call' with explicit components (market state, momentum, RSI, MACD, 4h trend, price walls, large transfers, bot activity, Bitcoin queue). This is a specific, non-tautological description that distinguishes it from more narrowly scoped sibling tools, 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 phrase 'Omit chain for all nine' and 'for every chain in a single report' implies the tool is for broad cross-chain overviews rather than single-chain or single-instrument queries. However, it does not explicitly state when to prefer this over siblings like market_state or chain_brief, nor does it offer exclusions or alternative routing.

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