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

Annotations only declare readOnlyHint and openWorldHint; the description adds the material behavioral fact that each call costs $0.003 USDC via x402, which an agent must know before invoking. It stays silent on rate limits, pagination, and how the limit truncates results, so it is not fully transparent.

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?

Two tight sentences with the core capability front-loaded and the cost caveat last; every clause earns its place and there is no filler.

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 three-parameter read tool with no output schema, the description covers the query modes and the payment requirement, which is most of what an agent needs. The unexplained 'limit' parameter and absent output-shape hint leave a small but real gap.

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 carries the burden: it explains that 'chain' scopes to one chain and 'protocol' retrieves that protocol's history, adding real meaning for two of three parameters. The third parameter, 'limit', is never mentioned or given units/semantics, so compensation is only partial.

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 resource (DEX trading volume) with concrete metrics (24h/7d volume with change) and enumerates the query modes, which cleanly separates it from siblings like defi_tvl, defi_fees and defi_yields. An agent can tell what this returns without opening the 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?

The three modes (overall, per-chain, single-protocol history) map onto the chain/protocol parameters, effectively telling the agent when to use each form, and example protocols (uniswap, aerodrome, raydium) are given. It never names alternative sibling tools or states exclusions, so it stops short of full alternative routing.

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