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

With no annotations provided, the description carries the burden of behavioral disclosure. It does add useful context by disclosing the pay-per-call cost ($0.005 USDC) and the 'live' nature of the USD value. It does not explicitly state that this is a read-only operation, but 'balance' strongly implies it.

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 short sentences with no filler: the first states the core functionality and scope, and the second surfaces the cost. Every word earns 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?

For a simple one-parameter balance tool with no output schema, the description is largely complete: it names the input, the output (native balance + USD value), the network scope, and the cost. It could add more detail about the output format, but the tool is simple enough that this is a minor gap.

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 100%, so the schema already documents the single 'address' parameter as a Base address. The description adds little beyond the schema beyond reinforcing that the address is any Base address and that the result includes live USD value.

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 that the tool returns the native balance and live USD value for a Base address, and the 'base address' phrasing distinguishes it from the polygon_* siblings. It lacks an explicit verb like 'get' or 'fetch', but the meaning is unambiguous.

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 implies usage whenever a caller needs a Base address's native balance and USD value. However, it provides no explicit when-to-use guidance, exclusions, or comparison to sibling tools such as base_token or base_stables, so the usage context is only implicit.

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