getTransactionReceipts

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

With no annotations, the description should disclose behavioral traits. It states a read operation (getting receipts) but omits details about response format, pagination, error handling (e.g., for invalid blocks), or any side effects. The description is minimal.

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 concise at one sentence (11 words), front-loading the key action and resource. No unnecessary words, meeting the standard for efficient communication.

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 no output schema and no annotations, the description should provide more context about what the tool returns or how to interpret results. It lacks details on the necessity of blockNumber or blockHash (implied but not explicitly stated in description) and any constraints on the block parameter. The input schema fills some gaps, but completeness is moderate.

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 baseline is 3. The description does not add meaning beyond the schema; it merely restates 'by number or hash'. The schema already documents the parameters well, so no additional value is provided.

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 tool retrieves all transaction receipts for a given block, specifying the filtering by block number or hash. It uses a specific verb (Get) and resource (transaction receipts), and distinguishes from siblings like debugGetRawReceipts by focusing on receipts for a 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?

No guidance is provided on when to use this tool versus alternatives such as traceBlock or debugGetRawReceipts. The description does not explain the context in which this tool is appropriate or when to prefer other tools.

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