Get block

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'fetch,' which hints at a read operation, but it does not explain what the returned block data contains, whether transactions are included by default, what block tags are supported, or how errors are handled.

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 sentence with no filler. The access methods are front-loaded and every word contributes to the meaning, making it easy to parse quickly.

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?

With four parameters, no annotations, no output schema, and low schema coverage, a one-sentence description is insufficient. An agent cannot determine important calling details such as valid blockTag formats, the effect of includeTransactions, or what the returned block data looks like.

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 only 25%, so the description must compensate. The phrase 'by block number/tag or by block hash' adds useful meaning for blockTag and blockHash, but includeTransactions remains completely unexplained by both the schema and the description, and chainId is already documented 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 verb ('Fetch'), the resource ('block data'), and the two access methods (block number/tag or block hash) on a chain. It is unambiguous, though it does not explicitly contrast with sibling tools; the resource is distinct enough that an agent can infer it from the sibling set.

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?

There is no guidance on when to use this tool instead of siblings like rpc_get_transaction, rpc_get_logs, or rpc_get_balance. The description implies it is for block-level data, but it never states exclusions, prerequisites, or alternative conditions.

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