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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the limit constraint (max 100, default 25) and the return format, but does not disclose additional behavioral traits such as rate limits, pagination, or permission requirements. Since the description carries less burden due to annotations, a score of 3 is appropriate.

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 well-organized: a concise purpose statement, a useful complement note, an Args section, and a Returns section. It is front-loaded with the core purpose, and every sentence adds value—the detailed return structure is necessary given the absence of an output schema. No redundant text.

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?

The tool has no output schema, so the description takes on the responsibility of explaining the return shape. It provides a comprehensive breakdown of the JSON response, including the funds array fields (manager, shares_change, direction, holding_value, etc.). Combined with parameter documentation and the relationship to the sibling tool, the description is complete for the tool's complexity.

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 provides only types and a default for limit, while the description's Args section adds significant meaning: ticker is explained as 'Stock ticker (e.g. 'AAPL')' and limit is described as 'Max funds to return (default 25, max 100)', including a range not present in the schema. This fully compensates for the 0% schema description 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 clearly states that the tool returns per-fund hedge-fund holdings and recent transactions for a ticker, with a specific list of fields (holding value, % of portfolio, rank/stars). It also distinguishes itself from the sibling tool get_hedge_fund_holdings by noting it complements the aggregate share-count timeseries, making the purpose and scope unambiguous.

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 explicitly mentions 'Complements get_hedge_fund_holdings (the aggregate share-count timeseries)', which indicates a usage distinction: this tool provides per-fund detail, while the sibling provides aggregate data. However, it does not explicitly state 'use this when you need X' or 'use that instead of Y', so the guidance is somewhat implicit rather than a full when/when-not directive.

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