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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real value beyond that: the data source (SEC Form 13F), that only the latest report period is returned, and the exact returned fields (investor name, shares held, market value, report period). No mention of rate limits or auth flow beyond the key example.

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?

Front-loaded with the core question ('Who holds <ticker>'), followed by a compact clarification and one example. The example largely duplicates the schema's examples block, so it is slightly redundant, but the definition stays short and readable.

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 fills the gap by enumerating return fields and the report-period semantics, and the annotations carry the safety profile. It stops short of pagination or result-ordering behavior, but for a simple filtered lookup it is nearly complete.

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 coverage is 100%, so the schema fully documents limit (default 25, max 200), ticker, and _apiKey. The description only restates limit's value via an example, adding no syntax or semantic detail beyond the schema; 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?

States a specific verb+resource: institutional 13F holders of a ticker (funds/asset managers reporting on SEC Form 13F). The framing ('who holds a stock') conceptually separates it from fd_insider_transactions (individual insiders) and fd_investor_portfolio (a fund's book), but no sibling is named explicitly to make the contrast airtight.

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?

The description makes the tool's domain obvious (institutional holders, latest 13F), so usage is implied. It never states when to prefer this over fd_filings, fd_insider_transactions, or fd_investor_portfolio, and offers no exclusions or prerequisites.

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