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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes beyond them by stating that dates, coverage and all data gaps accompany the result and that a shareable checkUrl is returned. It does not explain what 'free-preview' restricts (e.g., holding count or data recency), which is the most consequential behavior to know.

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?

Five tight sentences, front-loaded with what the tool produces and followed by input rules and return info; no filler. Slightly dense and rule-heavy, but each sentence carries operative 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?

With no output schema, the description carries the return-value burden and does so partially: it names the accompanying metadata (dates, coverage, data gaps) and checkUrl. Given only 2 parameters and simple nested structure, this is nearly complete, though the 'free-preview' limits and failure modes remain unexplained.

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 low, but the description compensates well: it requires exactly one ISIN or ticker per holding, warns tickers can be ambiguous across exchanges, mandates positive relative weights or values in a single base currency, allows omitting all amounts for equal weights, and forbids mixing weights and values. These constraints are not all expressed in the schema (oneOf covers identifier exclusivity only).

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 states a specific verb (analyze) and named outputs (overlap/concentration, ongoing charges, regional/sector exposures) for a portfolio of ETF holdings, which is clearly distinct from the sibling fund-comparison/ranking/search tools. It stops short of explicitly naming those siblings, but the resource and scope are 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?

The text explains how to format inputs (one ISIN or ticker per holding, weights vs values) but never says when to choose this tool over compare_funds or rank_funds, nor when-not to use it. 'Free-preview' implies limited scope without clarifying boundaries, so an agent gets no selection guidance.

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