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

With no annotations, the description carries the full burden, and it does disclose a genuinely useful behavior beyond the schema: wallet addresses are returned as pseudonyms (wallet_…) and never in clear. However, it says nothing about whether this is a safe read-only call, its scope (single portfolio vs all), or any rate/permission constraints.

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 that puts the return value first and the privacy caveat second, with no wasted preamble. The clause 'as pseudonyms (wallet_…), never in clear' restates the same idea twice, a minor redundancy.

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?

There is no output schema and no annotations, so the description is the only specification. It conveys what is returned and the pseudonymization behavior, but leaves the result shape (one address per portfolio? a list?), ordering, and error/empty behavior unspecified.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly introduces no parameter discussion. There is no parameter-level meaning left to add or omit.

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 ('Returns') and resource ('the wallets of each portfolio'), so the agent knows exactly what it fetches. It does not name or distinguish itself from the closest sibling, get_portfolio, so differentiation is left to inference.

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 statement of when to use this tool versus get_portfolio, get_pnl, or any other portfolio-scoped sibling, and no prerequisites or exclusions are given. Usage is only implied by the name.

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