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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behaviour beyond that: unknown facts are returned as null rather than omitted, and the response carries a shareable checkUrl. It does not mention rate limits or latency, but the key behavioural traits are disclosed.

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?

Three tight sentences with zero filler; the 50/50 portfolio scope and returned fact set are front-loaded, followed by the identification constraint and the checkUrl note. Every clause earns its place.

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 burden of explaining returns, and it names the main result components plus the checkUrl and null-handling convention. It does not enumerate the full response shape (e.g. how overlap is expressed), leaving a small gap, but it is sufficient to call the tool correctly.

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 coverage is 100% and the schema's oneOf constraints already enforce exactly one identifier per side, so the description's 'exactly one ISIN or ticker' restates structured data. The ambiguity caveat for tickers also duplicates the schema's own ticker description, so no meaningful parameter detail is added beyond the schema baseline.

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 and resource ('Analyze two ETFs as a 50/50 portfolio') plus the exact fact set returned (overlap, issuer facts, dated ongoing charges, region and sector exposure). This is clearly distinguishable from sibling list/search tools like search_funds, rank_funds, and the multi-holding xray_portfolio.

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 description specifies the identification rule ('exactly one ISIN or ticker' per side) and warns that a ticker can be ambiguous across exchanges, which is genuine usage guidance. It stops short of explicitly stating when to prefer this over xray_portfolio, but the context needed to invoke it correctly is clear.

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