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

Annotations already mark this tool as readOnly and non-destructive, so the description is not burdened with the full safety profile. It adds that the read targets a current USDC balance, but provides no additional behavioral detail such as default-token behavior, edge cases, or error handling.

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; it states the verb and object immediately. 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?

With no output schema, the description does not explain the return value, and it never states whether 'address' or 'token' are expected given that no parameters are required. An agent lacks enough detail to know defaults or output shape, so the description is not complete on its own.

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?

All three schema properties have descriptions, so schema coverages is high and the description does not need to carry parameter details. The description adds little semantic value for the parameters and may create confusion by calling the balance 'USDC' when the schema accepts a generic ERC20 token address.

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 a specific verb ('read') and a specific resource ('current USDC balance for an address'), making the core action clear. However, it does not distinguish this from sibling balance-related tools, and its 'USDC' claim sits awkwardly alongside the generic 'token' parameter in the schema.

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 mention of when to use this tool over alternatives or any exclusions, despite a large sibling set that includes peer_stake_balance and several balance-adjacent tools. An agent receives no routing guidance.

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