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

No annotations are provided, so the description must carry the full burden. It discloses the critical behavioral trait: this is a paid tool requiring a two-step payment process. It also clarifies search behavior for name fragments. It does not mention rate limits or output details, but the core non-obvious behavior (payment flow) is well explained.

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 concise and well-structured: main purpose first, then usage examples, then payment instructions, then an alternative tool. Every sentence contributes useful information without fluff.

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 the tool's complexity (paid, two-step, search) and lack of output schema, the description covers the key invocation details, payment flow, and alternative pricing tool. It does not describe the exact return format, but holdings data is implied and not critical for invocation. Overall it provides sufficient context for correct usage.

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 coverage is 100%, so the schema already documents both parameters. The description adds value by explaining that 'manager' accepts a CIK or a name fragment for searching, and clarifies that 'x_payment' is an optional signed payload with a specific purpose (settle payment after receiving terms). Examples further reinforce semantics.

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 the tool returns an institutional manager's 13F holdings for the latest quarter, with a specific verb ('Pass a CIK') and resource. It distinguishes itself from siblings by focusing on manager-level portfolio holdings and explicitly contrasts with the 'pricing' tool for price data.

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?

Provides explicit usage instructions: pass a CIK or name fragment to search, and explains the paid two-step flow (omit x_payment to get terms, then call again with signed payload). It also directs users to the free 'pricing' tool for prices, giving a clear alternative. However, it doesn't explicitly distinguish when to use this vs. 'holdings_changes' or other siblings.

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