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

With no annotations provided, the description carries the full burden. It discloses payment/authentication requirements (API key or payment options), and importantly states that failing sections are reported as 'unavailable'—a behavioral trait. However, it does not mention idempotency, rate limits, or error handling beyond partial failures. Still, for a read-only tool, it covers key behaviors.

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 dense sentence but packs essential information without fluff. It front-loads the payment requirement and then clearly states the tool's output. It could be split into two sentences for readability, but it is appropriately sized and structured.

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 tool's complexity (aggregating many data types) and minimal schema, the description adequately covers what it returns and the partial failure behavior. Since an output schema exists, return format is likely defined there. It misses some details like response structure or limits, but for a one-shot read tool, it is sufficiently complete.

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%, so the description must add meaning. It does not explicitly define the 'chain' parameter but states 'One chain' and notes that Bitcoin includes mempool data, adding context. The enum itself lists chain names, which is self-explanatory. The description adds marginal value but does not fully compensate for the lack of schema descriptions, though the single enum parameter limits the need.

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: it provides a comprehensive single-answer market overview for a selected chain, enumerating the specific data types (market state, momentum, price walls, large transfers, bot activity, open interest, stablecoin flows, and mempool for bitcoin). This distinctively positions it as an aggregate tool versus the granular sibling tools like market_state or stablecoin_flows.

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 for a holistic chain read ('the whole read in one answer') but does not explicitly state when to prefer this over individual metric tools or when not to use it. It lacks direct comparison to alternatives, though the sibling list makes it clear many specialized tools exist. The payment/API key requirement is mentioned, which is a prerequisite rather than usage guidance.

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