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

With no annotations provided, the description carries the disclosure burden and adds important context: it is a read-style balance lookup, returns formatted values with symbol and decimals, requires no API key or account, and costs $0.005 per call via x402 USDC. It does not cover failure behavior or rate limits, but the key operational traits are present.

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 front-loaded with the primary use case, then exclusions, then operational details like authentication and pricing. Every sentence adds useful routing or behavioral information.

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 read-only portfolio lookup with three parameters, the description covers the return contents, single-chain scope, batch behavior, and payment/auth model. It lacks exact output field names or error semantics, but no output schema is provided and the essential context is otherwise sufficient.

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 chain, token list, and wallet address parameters. The description reinforces that balances are returned for every listed token on one chain, but it does not add syntax or constraints beyond the schema.

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 states a specific resource and action: retrieve a wallet's native balance plus the balances of listed tokens on one chain in a single call. It also explicitly distinguishes itself from sibling tools for single-token balance and token pricing.

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?

It names both the intended use case and the exclusions: do not use for a single token (/v1/evm/erc20-balance) or for token valuation (/v1/evm/token-price). This gives an agent explicit routing guidance among sibling tools.

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