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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds meaningful behavioral context: data comes from quarterly 13F filings, funds not yet filed for the newest quarter are carried at prior-quarter positions (noted in output), and the percentage is relative to total institutional 13F shares, not shares outstanding. This goes beyond basic read/write disclosure.

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 three sentences and efficiently communicates the core function, data source, a key caveat, and a usage note. It is front-loaded with the primary purpose and avoids fluff. It is slightly verbose in the middle sentence but every clause adds information, so it earns a 4 rather than a 5.

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?

Without an output schema, the description appropriately covers what the return list includes (ranked institutions, shares held, market value, percentage) and highlights the data freshness caveat. The parameter schema handles input details. For a read-only data retrieval tool, this is sufficiently complete, though it does not mention pagination or count limits beyond the schema's maxResults clamp.

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 all three parameters (ticker, maxResults, reportDate) are already documented. The description itself does not add parameter-level detail beyond what the schema provides; it only subtly contextualizes reportDate through the 13F quarterly filing note. This matches the baseline of 3 for high schema coverage.

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 explicitly states the tool gets top institutional holders from SEC 13F-HR filings, with a specific verb and resource. It distinguishes itself from siblings like GetFundsHoldingStock by emphasizing 'top institutional holders (fund managers)' and the 13F data source. The return content (ranked list, market value, percentage) is also clearly specified.

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 provides clear context for when to use the tool ('Use this to understand who the major institutional investors in a company are'), but does not explicitly mention when not to use it or direct to alternative tools. Since it names a specific use case, it earns a 4 rather than a 3.

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