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

No annotations are provided, so the description carries the full behavioral burden. It implies a read via 'Get' but says nothing about whether the address may be a contract, whether invalid addresses error or return zero, or how the chain is selected (Base is hardcoded or implicit).

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though arguably too terse for a tool that returns an untyped value.

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 is simple (one param, read-only) and there is no output schema, so the description should ideally state the return units (wei vs. formatted ETH) and error behavior. Neither is covered, leaving a genuine gap for a value-returning tool.

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%, and the single parameter is fully documented with its format ('EVM address (0x + 40 hex)'), so the schema does the heavy lifting. The description adds no parameter meaning beyond what the schema already provides, which is the baseline 3 case.

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?

States a specific verb (Get), resource (ETH balance), target (an address), and scope (on Base). The resource name implicitly distinguishes it from the sibling get_usdc_balance, so an agent can route correctly, but the description never explicitly differentiates from siblings.

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?

No when-to-use guidance and no alternatives named, despite a dense sibling set including get_usdc_balance and get_address_risk_score. The agent must infer from the resource name alone that this is a plain balance read rather than a risk or label lookup.

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