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

Annotations already indicate read-only, idempotent, open-world, and non-destructive behavior. The description adds that results are 'compact summaries,' which aligns with the annotations. No contradictions, and the description adds modest context beyond the annotations.

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?

Two efficient sentences, no wasted words. The first defines the tool's action, the second offers guidance for a related tool. Perfectly front-loaded and compact.

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 that the tool has an output schema (not shown), the description need not detail return values. It mentions pagination indirectly ('page through'), and the parameters for pagination are well-defined in the schema. A slight gap: it doesn't explicitly state that results are a list of summaries, but the output schema likely covers this.

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 description does not explain any parameters. Schema description coverage is low (33%), with only the 'query' parameter having a description. The description should compensate for this gap but fails to do so, leaving the agent with no additional meaning beyond the schema.

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 it searches and pages through compact tracked 13F manager summaries, specifying the resource ('tracked 13F manager summaries') and verb ('search and page through'). It distinguishes from the sibling tool 'get_fund' by directing users there for positions and moves.

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 a clear alternative ('Use get_fund for positions and moves'), implying when not to use this tool. However, it does not explicitly state scenarios where list_funds is preferred or excluded, though the context is sufficient.

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