base_block

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does add useful context by disclosing pay-per-call cost ($0.005 USDC) and support for the 'latest' keyword. It does not mention auth, rate limits, or error behavior, though the read-only nature of a block lookup is reasonably implied.

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?

Two sentences with no wasted words: the purpose, supported lookup value, returned fields, and pricing are all front-loaded. Every clause adds useful information.

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?

For a simple two-parameter lookup, the description covers purpose, return fields, and cost. It is incomplete on the 'fields' parameter semantics and provides no error or fallback behavior, and there is no output schema to compensate for those gaps.

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 documents 'number' clearly, and the description reinforces it by saying 'block number or latest'. However, the 'fields' parameter is a bare string with no schema description, and the description only lists possible output fields without explaining how to use the parameter, its accepted format, or its default behavior.

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 names the resource (a Base block) and enumerates the returned data: hash, timestamp, tx count, gas used, and base fee. It also specifies the accepted lookup form, block number or 'latest'. It does not use an explicit verb like 'get' or 'fetch', and it does not explicitly distinguish itself from sibling polygon_block, so it stops short of a 5.

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 about when to use this tool versus alternatives. An agent must infer from the base_* prefix and sibling set that this is the Base-chain block lookup. No prerequisites, exclusions, or alternative tools are mentioned.

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