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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Search', implying a read-only operation, but does not disclose response format, pagination, behavior when manager is omitted, data freshness, or any limitations. This is insufficient for an agent to predict the tool's behavior beyond the basic action.

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?

A single sentence, front-loaded with the core action and resource, followed by concrete examples. No wasted words; every part contributes to understanding the tool's scope.

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 one optional parameter, no output schema, and no annotations, so the description must explain return values and edge cases. It does not state what the search returns (e.g., list of filings, metadata), nor what happens when 'manager' is omitted. This leaves the agent guessing about expected output and behavior, making it incomplete for correct invocation.

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% – the single parameter 'manager' already has a description with examples. The description repeats these examples without adding new meaning, so it does not compensate for any gap. With full schema coverage, the baseline of 3 is appropriate.

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 states a specific verb ('Search'), a resource ('SEC 13F institutional whale holdings'), and a clear scope ('major funds' with named examples). This distinguishes it from siblings like analyze_sec_filing, which implies analysis rather than search.

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?

Usage is implied by the example fund names and the action verb, but there is no explicit guidance on when to choose this tool over alternatives, nor any stated exclusions. The agent can infer it is for searching specific fund holdings, but the description does not explicitly say 'use this when you need to look up filings for these funds' or mention any sibling.

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