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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: values are 'as-filed' (not adjusted), and it warns of a 'public-reporting-lag' issue, which materially affects result interpretation. No return-shape or pagination detail, but that is minor given annotations.

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?

Two dense sentences that are front-loaded with the core purpose and scoped immediately to the corpus. Nearly every clause carries information; the return-value enumeration is slightly list-heavy but still 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 correctly compensates by enumerating the returned fields (percentages, security identifiers, report date, accession, quarter) and flagging the reporting lag. Resolution methods and return contents are both covered, so an agent has enough to call it 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 description coverage is 100%, so both parameters are already documented, making 3 the baseline. The description reinforces the accepted identifier forms for 'fund', but adds no syntax, matching rules, or constraints beyond what the schema states, and says nothing about 'limit'.

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 (List) and resource (largest holdings for a fund) and names the exact corpus (self-hosted SEC Form N-PORT), which separates it from the sibling nport_compare_funds. An agent knows this is a per-fund holdings lookup rather than a cross-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 gives input-resolution guidance ('Resolve by EDGAR series ID, mapped ticker, or fund-name substring'), which is useful, but never states when to choose this tool over nport_compare_funds or any other alternative, and offers no exclusions or prerequisites. Usage is implied rather than directed.

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