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

With no annotations provided, the description carries the burden of explaining behavior. It conveys that the tool is a read-only analytical API returning breakdowns and insights, but it does not disclose pagination behavior, response structure, or potential limitations. This is adequate but not thorough.

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 two sentences and reasonably concise. It front-loads the tool's primary purpose, though the second sentence is somewhat promotional and could be trimmed. Overall, it is efficient and easy to scan.

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?

Given the tool's moderate complexity (5 params, no output schema, no annotations), the description provides a decent high-level summary of what the response might contain ('analytical breakdown', 'stock movements', 'portfolio changes'). However, it does not explain the return format, pagination details, or any special constraints beyond the schema, leaving some ambiguity.

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 input schema provides 100% description coverage for all five parameters, so the description does not need to compensate. The description adds context that the data is organized by holder and relates to portfolio changes, but it does not add meaning beyond the schema's explicit parameter descriptions.

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 clearly states the tool provides an analytical breakdown of institutional filings for a given symbol, year, and quarter, focusing on major institutional holders. It distinguishes itself from related filing tools by emphasizing the 'analytics' angle (stock movements, strategies, portfolio changes), though it does not explicitly name sibling alternatives.

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 offers no explicit guidance on when to use this tool versus other filing-related tools like getFilingsBySymbol, getLatestInstitutionalFilings, or getForm13FFilingDates. It implies usage for analyzing institutional holdings but does not state exclusions or alternative tool recommendations.

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