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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds valuable nuance: it mentions the multi-series trust caveat (only tracked-stock positions stored) and clarifies that reported counts still reflect the full filing. This goes beyond what annotations provide without contradicting them.

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?

The description is front-loaded with the purpose and then details, caveat, and alternative. It is slightly dense but every sentence adds value. It avoids fluff and is appropriately sized for a tool that returns a profile plus holdings.

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?

While there is no output schema, the description lists the returned fields (registrant, series, assets, holding counts, largest positions) and notes the multi-series trust caveat. It also references the inverse tool. For an agent, this is sufficient to understand return expectations and when to use the tool, though it does not mention error cases or pagination beyond maxResults.

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?

The schema covers both parameters with descriptions, and the tool description adds extra meaning by explaining the accepted identifier types and giving examples (e.g., 'S000004344', 'IWM'). The maxResults description is also clear with default and max. The description enriches the schema rather than merely repeating 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?

The description states a specific verb and resource ('Get a registered fund's profile and largest stored holdings') and clearly distinguishes it from the inverse lookup tool GetFundsHoldingStock. It leaves no ambiguity about what the tool does.

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 details acceptable input types (profile ID, SEC series ID, ticker, alias) and references SearchFunds for verified aliases. It points to GetFundsHoldingStock for the inverse lookup, but doesn't explicitly state conditions for choosing alternative tools beyond that. This is clear context, though a short 'use when' clause would strengthen it.

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