1s_block_by_number

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

Mentions it's via RPC and lists returned fields (transactions, gas, miner, timestamp). However, no annotations provided; lacks disclosure on auth needs, rate limits, or error handling (e.g., invalid block number).

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 efficient sentences: first states purpose and returns, second specifies number format. No fluff or redundancy.

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?

Adequately covers purpose, parameters, and return fields for a simple block detail tool. Lacks mention of output schema, but not critical given its straightforward nature.

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 coverage is 100% and schema descriptions already detail both parameters. Description adds minor clarification on number format (decimal or hex) but doesn't go beyond what schema 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?

Clearly states it gets full block details by block number via RPC, listing key return fields. Distinguishes from sibling '1s_block_number' which likely returns only the current block number.

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?

Implicitly for retrieving block details, but no explicit when-to-use vs alternatives or prerequisites. Could compare to other tools like '1s_tx_details_live' for transaction-level queries.

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