get_uncle_blocks

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

With no annotations, the description carries the burden of behavioral disclosure. It adds conceptual value by explaining what uncle blocks are, but it does not mention return format, pagination, errors, or any side effects. For a read-only tool, this is adequate but not rich.

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 two sentences long, front-loaded with the core action ('Get uncle blocks for a specific block') and immediately followed by a clarifying definition. Every word earns its place; there is no 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?

The tool is simple, with a complete input schema and no output schema. The description explains the concept (uncle blocks) and the target (a specific block), which is enough for an agent to understand what the tool does. It could mention the return value shape, but given the simplicity, it is reasonably complete.

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 100%, so the schema documents both network and blockNumber well. The description adds no additional parameter semantics beyond what the schema already provides, such as format or default behavior. Baseline 3 is appropriate.

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 uses a specific verb ('Get') and resource ('uncle (ommer) blocks') and clearly scopes it to 'a specific block'. It also defines the concept of uncle blocks, which distinguishes it from sibling block retrieval tools like get_block_by_number or get_latest_block.

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 clearly implies when to use the tool: when you need uncle/ommer blocks for a particular block. It does not explicitly name alternatives or exclusions, but the context is clear. The emphasis on 'specific block' and the required blockNumber parameter provide clear usage context.

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