DEX wallet portfolio

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's addition of 'Token holdings' confirms the read operation. No further behavioral details (e.g., pagination, error handling) are disclosed, but the annotations carry much of the burden.

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 a single sentence of 7 words that perfectly conveys the purpose. No extraneous information, and it is front-loaded with the key action and resource.

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 tool with two well-described parameters and no output schema, the description provides essential context. Minor additional detail about the return format (e.g., list of tokens with balances) could enhance completeness, but it is adequate for effective tool selection.

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%; both chain and address have clear descriptions. The tool description does not add additional meaning beyond the schema, meeting the baseline expectation.

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 'Token holdings for a wallet on an EVM chain.' clearly states the verb (retrieve) and resource (token holdings) and scope (wallet, EVM chain). It distinguishes from sibling tools, which are mostly stock and market data tools, none of which involve DEX or wallet holdings.

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 implicitly indicates use when token holdings are needed for a wallet on an EVM chain. Given the unique purpose among siblings, alternatives are not obvious, so no explicit exclusions are necessary. A clear usage context is provided.

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