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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful scoping context beyond that: it never accepts a user id and never returns another user's data, which tells the agent about authorization boundaries and confirms there is no cross-user leakage.

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, no filler: the usage trigger is front-loaded and the access boundary follows. Every clause carries information an agent needs.

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 values need not be described, and annotations cover the safety profile. The remaining gap is the optional portfolio_name selector, which is undocumented in both schema and description — an agent cannot tell whether omitting it returns all portfolios or a default one.

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% for the single parameter portfolio_name, so the description carries the full burden and fails to mention it at all. It never explains whether the name selects one portfolio among several, what happens when it is null (the schema allows null), or what valid values look like.

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 gives a specific verb+resource (review the authenticated user's own ValuEdge portfolio) and enumerates the content it covers: holdings, market value, fair-value coverage, allocation, concentration, risk context. It does not explicitly distinguish itself from the very similar sibling analyze_my_portfolio, so an agent must guess which to pick when the user asks for analysis rather than a plain read.

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 is an explicit use-when trigger ('when the authenticated user asks to review their own... portfolio'), which is stronger than most tool descriptions. However, no alternative is named or excluded, and analyze_my_portfolio sits directly adjacent in the sibling list with no guidance on which to choose.

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