get_block

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

No annotations are provided, so the description must disclose behavioral traits. It indicates it is a read operation by using 'Get', and mentions optional fullTransactions. However, it does not describe error handling (e.g., if block not found), rate limits, or authentication needs. Given no annotations, this is adequate but not comprehensive.

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 concise sentences. The first states purpose and acceptable inputs; the second provides a key usage hint. No extraneous words or repetition. Well-structured for quick parsing.

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?

Despite having only 3 parameters and no output schema, the description does not explain what the tool returns (e.g., block details, structure). It only covers the fullTransactions option. For a block retrieval tool, agents need to know the response format to process results. This is a significant 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 coverage is 100%, so the schema already documents all parameters. The description adds value by clarifying the meaning of block (number or tag with examples) and fullTransactions (include full tx objects instead of hashes), which supplements the schema descriptions.

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 verb 'Get' and resource 'block', specifying acceptable inputs (number or tag). It distinguishes from siblings like get_block_number (which gets the latest block number) and get_transaction (which gets a specific transaction). However, it does not explicitly contrast with all siblings.

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 provides a usage hint for the fullTransactions parameter, but does not offer explicit guidance on when to use this tool versus alternatives (e.g., get_block_number for latest block number, get_transaction for individual transactions). The context from sibling tools helps, but the description itself could be more explicit.

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