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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not repeat safety. It adds value by enumerating returned fields (as-filed values, portfolio percentages, security identifiers, report date, filing accession, public-reporting-lag warning), which gives agents confidence about what the call returns.

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?

It is a single, well-front-loaded sentence that immediately communicates the core operation and then enumerates return fields. No fluff or repetition; could arguably be split into two sentences but it is still efficient.

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 compensates by enumerating the return fields and warning signifier. It covers the data source and resolution input. It doesn't mention error behavior, but for read-only holdings list the most critical details are present.

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%, so parameters are already documented. The description adds the 'fund-name substring' nuance and the notion of 'largest holdings,' which the schema does not specify, but it doesn't go beyond that to substantially augment the parameter docs.

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 uses the specific verb 'list' and names the resource 'largest holdings for a fund,' with an explicit data source (SEC Form N-PORT corpus) and three resolution methods (EDGAR series ID, mapped ticker, fund-name substring). This clearly distinguishes the tool from nport_compare_funds, which seems to target multiple-fund comparison.

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?

It states how the fund can be identified (EDGAR series ID, ticker, or name substring), giving clear usage context. However, it provides no guidance for choosing this tool over its sibling nport_compare_funds and no exclusions or alternative recommendations.

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