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

With no annotations, the description carries full behavioral transparency. It discloses a key behavioral trait: cost sharing/reuse where answers cached by other agents reduce cost and earn credit for the producing wallet. This goes beyond simple read behavior and aids expectation setting.

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 three sentences, front-loaded with the core purpose and supported by pricing and reuse details. It is not overly verbose, though the cost explanation could be shortened without losing clarity.

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 no parameters and no output schema, the description adequately explains what the tool returns and the pricing model. It is complete enough for an agent to understand the tool's purpose and operational context, though it lacks explicit return format or error handling.

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 input schema has zero parameters and is fully covered (100%). The description clarifies that no parameters are required and adds meaning by listing the returned data fields, which is useful since no output schema is provided.

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 tool retrieves the current state of Base, listing specific data points (latest block number, timestamp, base fee, suggested gas fees) and emphasizes it requires no parameters. This distinguishes it from sibling tools that deal with contracts, evidence, and transactions.

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 context on when to use the tool (getting current state cheaply) and the cost model, but does not explicitly contrast with sibling tools or state when not to use it. An agent must infer exclusivity from the sibling names.

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