get_transaction_info_by_block_num

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

Annotations already provide readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds that it returns receipts for all transactions in a block, but it does not clarify pagination, response structure, or network-specific behavior beyond what the schema already states.

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 front-loaded sentence that immediately names the action, resource, and scope. No unnecessary words or repetition, making it efficient for an agent to parse.

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 simple 2-parameter schema, strong annotations, and no output schema, the description is largely complete. It could be more explicit about returning a list/array of receipts and mentioning the optional network parameter, but these are inferable from the schema and the word 'all transactions.'

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%, with clear descriptions for both parameters ('Block height number' and 'Network name. Defaults to mainnet.'). The tool description adds no extra parameter meaning; it simply restates the block-height focus already present in the schema.

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 action ('Get'), the resource ('TransactionInfo (receipts)'), and the scope ('for all transactions in a specific block height'). This distinguishes it from sibling tools like get_transaction_info (which likely retrieves a single transaction's info) and get_block_by_num (which retrieves block data).

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 implies when to use it (when you need all transaction receipts for a given block height), but it does not explicitly state alternatives or when not to use it. There is no mention of using get_transaction_info for single transaction lookups, which is a key sibling distinction.

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