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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. On top of that, the description adds meaningful behavioral detail by enumerating the return content (per-wallet match status, token count, last transaction time, overall match flag) and clarifying that the tool performs a comparison rather than a mutation. No contradiction with annotations; the added disclosure is genuinely informative.

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, dense sentence with no filler: the purpose clause is front-loaded and the return items trail in a compact list. Every phrase earns its place. It could be split for readability but is efficient and well-ordered as written.

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 correctly shoulders the duty of disclosing return values and does so (match status, token count, last transaction time, overall flag). For a simple two-parameter read-only lookup with strong annotations, nothing critical is missing. Minor gaps — the precise meaning of a 'match' failure or behavior when no snapshot exists — are edge cases an agent can discover by calling the tool.

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 workspaceRef and portfolioRef are documented as 'exact name or slug' in the schema. The description adds no additional parameter semantics beyond what the schema already provides. Per the high-coverage baseline, a 3 is appropriate since the schema carries the full burden and the description does not need to compensate.

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 action ('check whether computed token balances match the latest synchronized snapshot') with a clear resource (per-wallet balances within a portfolio). The verification/consistency framing distinguishes it from sibling get tools like get_asset_position, get_wallet, and get_portfolio, which fetch positions directly. However, the name and title ('Get Portfolio Balances') suggest a straightforward balance retrieval, so there is a mild tension between the name and the actual compare-and-report behavior.

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 gives no guidance on when to invoke this tool versus alternatives. With 44 siblings covering reconciliation-adjacent duties (get_sync_status, full_resync, get_portfolio_issue_summary, get_asset_position), the description does not state when a match check is appropriate, nor when one of those siblings would be a better choice. The use case (verify balances against snapshot) is only implied, never made explicit.

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