get_block_by_number

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'Get a block by number' and provides no information about return format, whether transactions are included, network behavior, or any side effects. The description adds no behavioral transparency beyond the tool's name.

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, but it's essentially a restatement of the tool name. It is under-specified rather than effectively concise, lacking necessary context about what a block includes or when to use this tool, so it doesn't earn its place.

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 has no output schema and no annotations, so the description should explain return values and usage context. It fails to mention what fields the block contains, how it differs from other block-related tools, or any network constraints. The description is too minimal to be complete for an agent selecting among many similar tools.

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?

The schema already describes both parameters with 100% coverage, including network defaults and blockNumber description. The tool description adds no extra meaning to the parameters, so it neither helps nor harms beyond the baseline provided by 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 states the verb 'Get' and the resource 'block by number', clearly indicating the core function. However, it doesn't distinguish this from sibling tools like get_block_by_hash, get_latest_block, or get_block_with_transactions, so it doesn't fully clarify what kind of block data is returned.

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 provides no guidance on when to use this tool versus alternatives, such as when to use get_block_by_hash or get_latest_block. It also doesn't mention network-specific usage or any prerequisites, leaving the agent without context for tool selection.

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