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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'provides a comprehensive snapshot' and 'over time'. It does not clarify whether the output is a time series, how the required year and quarter parameters affect the response, or any other behavioral traits like data source or limitations.

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 mostly efficient, but phrases like 'provides a comprehensive snapshot' are somewhat vague and could be more direct. Still, it avoids redundancy and presents the key information in a structured way.

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 there is no output schema, the description does not explain what the returned data looks like, whether it is a point-in-time summary or a time series, or how the year/quarter inputs shape the result. It also lacks usage guidelines, making it incomplete for a tool with three required parameters.

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 already has 100% description coverage for all three parameters (symbol, year, quarter), so the baseline is 3. The tool description adds no substantial meaning beyond what the schema states, though it reinforces that the data is for a specific stock and over time.

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 what the tool does: provides a comprehensive snapshot of institutional holdings for a specific stock symbol, with details on metrics like investor count and share changes. It uses a specific verb and resource, but does not explicitly differentiate from sibling tools like getFundHoldings or getLatestInstitutionalFilings.

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 gives no guidance on when to use this tool over alternatives or any exclusions. It implies usage for getting institutional holding summaries, but does not mention any circumstances, prerequisites, or related tools.

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