get_base_block_number

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

With no annotations, the description itself must convey behavioral expectations. The verb 'Get' indicates a safe read-only operation. The tool has no parameters and no side effects, so there is little additional behavior to disclose. It doesn't explain return format or error cases, but these are not critical for such a straightforward getter.

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 that immediately states the action and resource. It contains no filler or redundant information, making it highly concise and well-structured for the tool's simplicity.

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 tool has no inputs and no output schema, the description adequately covers what the tool does and what it returns (the current block number). It lacks detail on return type or potential delays, but this is a minor gap. Overall, the description is sufficiently complete for an agent to select and invoke the tool correctly.

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 tool takes zero parameters, so the input schema is fully complete. The description adds no parameter semantics, but none are needed. The baseline of 4 for zero parameters is appropriate.

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 uses the specific verb 'Get' and identifies the exact resource 'current Base blockchain block number'. It clearly distinguishes itself from siblings like get_base_gas_price, get_base_balance, and lookup_erc8004_agent, which serve different purposes.

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 makes it clear that this tool is for retrieving the current block number on Base. While it doesn't explicitly state alternatives, the sibling tools cover different resources, so the usage context is unambiguous. There are no exclusions or prerequisites mentioned, which is appropriate for a simple read-only tool.

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