get_block

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

With no annotations provided, the description should disclose behavioral traits. It does not mention side effects (none expected), return value format, error handling for invalid inputs, or any authentication requirements. The description is minimal and leaves the agent to infer behavior.

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, 13-word sentence that conveys the essential purpose without any superfluous information. It is optimally concise and front-loaded.

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 simplicity of the tool (2 optional parameters, no output schema, read-only), the description is adequate but lacks critical details such as the return structure or behavior when the block does not exist. It does not consider the context of sibling tools to position itself.

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 50% (only 'block' has a description, and it is generic: 'Block number or tag'). The tool description adds value by specifying valid formats for the 'block' parameter, but it completely ignores the 'includeTransactions' parameter, which is not described anywhere.

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 specifies the verb 'Get' and the resource 'block', and enumerates the accepted formats ('latest', 'earliest', decimal height, hex height). This distinguishes it from sibling tools that deal with blocks in different contexts (e.g., latest_blocks, block_transactions).

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention conditions where it might not be appropriate. It only states what it does.

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