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

With no annotations, the description carries the full burden and does so superbly. It discloses data sampling methods (sampledBlocks/totalBlocks), null vs. zero handling for fees, missing-hour semantics, the staleness flag, and explicitly labels the inferred revenue as a 'LABELLED ESTIMATE, never reported revenue.' This is exemplary behavioral disclosure.

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 paragraph but every sentence adds substantive value—no filler. It could be slightly improved by breaking into bullets, but it remains efficient and well-ordered, front-loading the core purpose before diving into data-quality caveats.

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?

The tool has no output schema, so the description must convey return content and behavior. It does comprehensively: metrics list, sampling method, edge cases (null fees, missed hours, stale flag), and folded windows. An agent can confidently call this tool and interpret results without further documentation.

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?

The single parameter 'hours' is fully described in the schema (default 72, min 1, max 720), and the description adds no additional parameter nuance beyond the schema. Since schema coverage is 100%, the baseline of 3 is appropriate; the description doesn't need to repeat what the schema already provides.

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 measures Robinhood Chain sequencer economics from blocks, listing specific metrics (transactions, gas used, L2 fees, contract deploys, ERC-4337 traffic). The scope is precise (hourly rollups, daily folds, labeled estimates) and distinct from the sibling tools, which are general stats or other chains.

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 doesn't explicitly name alternatives or when not to use this tool, but it strongly implies its use case: analyzing sequencer economics, fee breakdowns, and subsidy-cliff impacts. The rich detail on what it returns (e.g., 30d daily fold, stale flag) makes its applicability clear, though it stops short of explicit comparison with chain_composition or get_chain_stats.

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