wallet_portfolio

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

Discloses it reads from public RPCs and joins live prices, indicating read-only behavior. No annotations exist, so description carries full burden; it's clear but does not mention any limits or authorization requirements.

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 sentences, front-loaded with key benefit, no fluff. Highly efficient.

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?

Explains output (native balances and top ERC-20s priced in USD) sufficiently for a portfolio tool. Vague on 'top' limit but no output schema exists; overall complete.

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 covers both parameters fully (100% coverage). Description does not add new parameter details beyond what schema already states, so baseline 3 applies.

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?

Clearly states the tool aggregates live multi-chain portfolio data including native coins and top ERC-20s, priced in USD, across five chains. Distinguishes from sibling tools focused on individual token or gas data.

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?

Explicitly recommends use when needing current on-chain holdings/net worth without many RPC calls. Does not exclude cases but implies when to use over siblings like token_price.

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