Fund Profile and Top Holdings

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

The readOnlyHint annotation covers the safety profile, and the description adds genuinely new behavior: the NPORT-P provenance, what is returned (registrant, series, assets, reported vs stored counts, largest positions), and a data-quality caveat that some multi-series trusts store only tracked-stock positions while counts and asset totals reflect the full filing. It does not discuss pagination behavior for the offset/maxResults window.

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?

Four tight sentences, front-loaded with purpose, then inputs, then return contents, then the sibling handoff. Every sentence carries information; the only mild redundancy is the restatement of accepted identifier forms already in the schema.

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?

For a three-parameter read tool with no output schema, the description covers source, accepted inputs, returned fields, and the stored-vs-reported caveat that an agent would otherwise get wrong. Pagination semantics are left to the schema, which handles them adequately.

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 the schema already documents all three parameters, including the accepted fund ID forms and the maxResults cap of 500. The description largely restates those accepted identifier types rather than adding format or syntax detail. Baseline 3 applies.

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 ('Get a registered fund's profile and largest stored holdings') plus the exact data source (latest SEC Form NPORT-P report). It explicitly names the sibling it is not — GetFundsHoldingStock is the 'inverse lookup' — so an agent can separate the two without opening either schema.

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?

Names the alternative tool and the condition that selects it ('Use GetFundsHoldingStock for the inverse lookup'), and points at SearchFunds as the source of a valid 'verified alias'. It stops short of stating when-not to use this tool, but the routing to the sibling is explicit and actionable.

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