search_blocks

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

No annotations provided, so description carries full burden. It discloses the 'Max 10 blocks' limit and inclusivity bounds, but fails to state whether exceeding the limit errors or truncates, or whether this is read-only/safe.

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?

Extremely efficient: two sentences for purpose+constraints, followed by structured Args documentation. No redundant text; every element earns its place.

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 simple 2-parameter integer schema and presence of output schema, the description is adequately complete. It covers the key operational constraint (max 10) that wouldn't be visible in the schema, though sibling differentiation would improve completeness.

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 has 0% description coverage. The Args section effectively compensates by explaining both parameters are block heights and specifying they are inclusive, adding critical semantic detail absent from 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?

Clear verb ('Get') + resource ('block statistics') + scope ('range of heights'). The mention of 'range' implicitly distinguishes from single-block siblings like analyze_block or get_block_stats, though explicit differentiation from search_blockchain is absent.

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?

States the constraint 'Max 10 blocks' but provides no guidance on when to use this versus siblings like get_block_stats (likely single-block) or search_blockchain. No mention of prerequisites or error conditions.

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