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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the dual data source and the fallback condition, plus the derived concentration metrics, which an agent would not infer from annotations alone.

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 front-loaded sentence with no filler, and the core scope comes first. It is dense but each clause (source, contents, metrics, share-class rule) earns its place; only the parenthetical metric list is slightly compressed.

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 needn't explain return structure, yet it still usefully enumerates the payload categories. For a two-parameter, read-only lookup tool this covers what an agent needs to call it correctly; only explicit sibling routing is missing.

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 100%, and both parameters are fully documented in the schema (ticker examples, limit range and ordering). The description's mention of 'the largest lines with their weights' only marginally reinforces the largest-first ordering already stated in the limit parameter, so the baseline 3 is appropriate.

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 and resource (an ETF's or index fund's holdings) and enumerates what comes back: largest lines with weights, sector mix, and concentration stats. It also names the fallback data source (issuer file vs. SEC N-PORT) and the share-class resolution rule, which clearly separates it from siblings like etf_overlap, who_holds, and fund_fees.

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 context is implied through the data-source fallback (issuer file first, SEC N-PORT for funds outside the catalog) and the share-class resolution behavior. However, there is no explicit guidance on when to pick this over etf_overlap or who_holds, and no exclusions are stated.

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