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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description still adds useful behavioral context beyond that: the exchange-suffix requirement for non-US symbols and a scope disclaimer about advice/prediction/tax. It does not say what happens on an invalid or ambiguous ticker, which is the one remaining gap.

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 resource and its returned fields, then examples, then the sibling alternative, then constraints — a sensible priority order. Slightly over-packed with example questions and a metric list, but no sentence is filler.

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, the description need not enumerate return values, and the read-only annotations cover the safety profile. Combined with routing to search_symbols for suffix discovery, an agent has what it needs to call this correctly; only failure handling for unknown tickers is unaddressed.

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 there is a single parameter, so the baseline is satisfied by the schema alone. The description nevertheless adds real operational meaning: single-ticker only, and the exchange-suffix convention illustrated with VWCE.DE and IWDA.AS, which is more actionable than 'as the exchange lists it'.

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 precise verb+resource: returns profile data for a single fund or share, enumerating the exact fields (name, type, exchange, cost, return, volatility, worst fall, top holdings and sectors). It explicitly separates itself from look_through (whole portfolio) and search_symbols (ticker discovery), so an agent can route between siblings without opening schemas.

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 concrete triggering questions ('What is EQQQ.DE?', 'What's inside VXUS?'), names the alternative for the portfolio-level case (look_through), and states the prerequisite that non-US tickers need an exchange suffix with search_symbols as the resolver. It also sets explicit exclusions: no recommendations, predictions, or tax calculations.

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