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

No annotations are provided, so the description carries the full burden, but it does disclose a real behavioral trait: the $0.10 USDC x402 pay-per-call pricing on Base. It omits return format, freshness/latency of 'live SEC filings', and any rate limits or failure behavior.

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 front-loaded sentence with the resource first and pricing last; nothing is redundant. The parenthetical pricing is dense but earns its place as the only cost signal.

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?

With no output schema, the description should describe what a search returns (fund list, holdings, filing dates) but does not. Scope, examples, and cost are covered, leaving the result shape and the behavior when 'manager' is omitted unstated.

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 single 'manager' parameter has 100% schema coverage with its own examples, so the baseline is 3. The description's parenthetical fund list duplicates the schema's example values rather than adding new semantics (e.g. partial matching, case sensitivity, whether omission returns all managers).

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?

States a specific verb and resource ('Search SEC 13F institutional whale holdings') and scopes it with named example funds, so an agent understands the domain immediately. It does not explicitly distinguish itself from the sibling 'analyze_sec_filing', which covers similar SEC ground.

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?

There is no when-to-use or when-not-to-use guidance, and no routing to alternatives even though a closely related sibling (analyze_sec_filing) exists. The only usage signal is implicit scope from the fund examples.

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