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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description goes further and adds context annotations cannot carry. It discloses pricing ($0.002/call, 10 free/day, x402 payment-required response) and error handling (isError with a message, not charged), plus the return shape (ranked, day-over-day change). This is exactly the value-add behavioral layer the dimension rewards.

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 definition is front-loaded with the resource and metric framing, then layers semantics, ranking behavior, pricing and error handling in compact sentences. Slightly dense, and the tagline "the cash-flow view of crypto" is decorative, but every substantive sentence carries operational information.

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?

With an output schema present, the description need not explain return values, and it does not try to. It instead covers what structured fields omit: metric definitions, pricing/payment flow, and error semantics, which is complete for a zero-required-parameter read-only ranking 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 100%, with limit, metric and chain all documented in the schema itself, so the baseline is 3. The description restates the fees-vs-revenue distinction and adds the 24h/7d/30d notion, but it does not document limit behavior or the default, so it adds only marginal meaning beyond the schema.

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 a specific resource (protocols and chains) and a concrete framing: ranking fees or revenue over 24h/7d/30d windows, filterable by chain. It clearly defines the two metric modes ("fees" = what users paid; "revenue" = what the protocol kept), which helps separate it from look-alikes such as defi_rankings or chain_tvl. It stops short of explicitly naming a sibling to contrast against, so it lands at 4 rather than 5.

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 cash-flow view of crypto" and "filterable by chain" imply when the tool is relevant, but there is no explicit when-to-use / when-not-to-use statement and no routing to alternatives like chain_tvl or defi_rankings. The metric enum is explained, but that is parameter semantics, not tool-selection guidance. Usage is therefore implied rather than spelled out.

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