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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuine behavioral constraint beyond that: output must explain evidence and limitations and must not issue buy/sell/hold instructions. It does not mention auth requirements or any rate/scope limits.

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 trigger condition is front-loaded and the behavioral constraint follows. The dense trigger list is long but every clause maps to a distinct analysis type 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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Purpose, usage context, and output-style constraints are all present; the only real gap is the meaning of the optional portfolio_name parameter.

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 single optional, nullable parameter portfolio_name is never mentioned. The description gives no hint that omitting it selects a default portfolio, which is the key ambiguity an agent faces here. With one undocumented param the description should compensate, and it does not.

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 enumerates the concrete analyses produced (concentration, sector/currency allocation, fair-value coverage, risk context), which lets an agent distinguish it from the raw-retrieval sibling get_my_portfolio. It never states the verb 'analyze' outright, but the enumerated outputs make the resource and scope 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?

It gives an explicit trigger ('when the authenticated user asks for their own portfolio...') and scopes it to the authenticated user's own data, implicitly excluding other users' portfolios and other siblings. It stops short of naming an alternative (e.g., get_my_portfolio for raw holdings) or stating when not to use it.

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