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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds real context beyond that: it discloses the shape of the returned enrichment and, importantly, that it returns null when the user has no portfolio — a non-obvious edge case. Auth requirement is implied by 'authenticated user's'. No rate-limit or latency notes, so not a 5.

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?

Front-loads the purpose, then the field list, then the trigger phrases — a logical order with no filler. The enrichment enumeration and the phrase list are long, but both carry selection value rather than padding.

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 an output schema present, annotations covering the safety profile, and no parameters to document, the description supplies everything an agent still needs: what it returns at a high level, who it applies to, and the null-return edge case.

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 per the rubric the baseline is 4. There is nothing for the description to disambiguate, and it correctly signals the tool is self-scoped to the authenticated user rather than requiring an ID argument.

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+resource ('Get the authenticated user's portfolio holdings') and immediately scopes it as personal/enriched, which separates it from the many company-level siblings like get_insider_ownership, get_performance, or get_dividends. The enumeration of enriched fields (prices, P&L, governance scores, insider trades, sector exposure) makes the resource unambiguous.

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?

Gives an unusually explicit use-condition with concrete user phrasings ('my portfolio', 'how am I doing', 'what should I worry about') and a catch-all for personal-portfolio questions. It does not name a when-not case or point to a sibling alternative, so it falls short of the top bar, but the routing guidance is clear and actionable.

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