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

With no annotations, the description carries the burden and does reasonably well: it discloses the price ($0.05), the conditional dependency (risk stats require return history), and the output shape ('ends with prioritized findings'). It does not state that the operation is read-only/non-mutating or what happens with missing sectors/targets, which keeps it below 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?

A single dense but well-ordered sentence puts the core outputs first, followed by conditional metrics and the closing 'prioritized findings', with price appended last. It is long but nearly every clause names a distinct output; only the price tag sits as a slightly detached addendum.

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?

There is no output schema, and the description compensates by enumerating the returned analyses, which is a real strength given the nested holdings objects and 9 parameters. Still, key input semantics (benchmark for beta, limits for concentration flags, periods_per_year annualization) are left undocumented, so an agent cannot fully specify a correct call from this description alone.

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 only 33% across 9 parameters, so the description must compensate and largely does not. It links 'returns' to the risk metrics and implicitly links 'targets' to drift, but says nothing about 'limits' (max_drawdown/max_sector_weight/max_single_weight), 'benchmark_returns' (which is what beta must consume), 'cash', or 'periods_per_year' — an agent could easily call it without a benchmark and get no beta.

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 ('periodic advisor review of a portfolio') and enumerates exactly what is computed: weights, HHI/effective holdings, sector and asset-class exposure, drift with rebalance trades, and the return-based risk metrics. No sibling tool (advisor_memo, strategy_audit, suitability_check) has this scope, so the agent can distinguish it without opening the schema.

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?

Usage is implied by 'periodic advisor review' and by the conditional 'given return history', which tells the agent that risk metrics only materialize when returns are supplied. However, there is no explicit guidance on when to pick this over advisor_memo or strategy_audit, and no exclusions or prerequisites stated.

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