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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is low. The description nonetheless adds a genuine behavioral guarantee beyond the annotations: it never accepts a user id and never returns another user's data, which is a meaningful scoping/security constraint for an agent. It omits what happens when no portfolio exists, but that is minor.

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, zero filler, with the usage trigger front-loaded before the scoping constraint. Every clause carries 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?

An output schema exists, so return-value explanation is not required, and annotations cover the safety profile. What remains missing is the interpretation of the single optional parameter and the disambiguation from 'analyze_my_portfolio', so the definition is nearly but not fully self-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 0% and the description never mentions 'portfolio_name' at all. Because the parameter is optional and nullable, the crucial question — whether null means default portfolio, all portfolios, or aggregate — is answered nowhere, so the description does not compensate for the coverage gap.

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?

It states a specific verb-plus-resource ('review their own ValuEdge portfolio') and enumerates the facets returned (holdings, market value, fair-value coverage, allocation, concentration, risk). It stops short of differentiating itself from the sibling 'analyze_my_portfolio', which sounds like the same resource and leaves the agent guessing which to pick.

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 opening clause gives an explicit trigger condition ('when the authenticated user asks to review their own... portfolio'), which is far beyond implied usage. However, it names no exclusions and never mentions the nearby 'analyze_my_portfolio' alternative, so the boundary between retrieval and analysis is left to inference.

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