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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds material behavior the annotations cannot: the x402 payment model ($0.01 USDC per call), the settlement rule (charged only when a result is returned; 400 and 4xx/5xx not settled), and the aggregation behavior (positions merged across sub-managers, options marked put/call). These are exactly the operational facts an agent needs before invoking a paid call.

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?

Front-loaded with the user questions the tool answers, then inputs, then output shape, then cost — a sensible ordering. The long parenthetical manager roster is somewhat bloated and partially redundant with the `fund` schema example, but every remaining sentence (return fields, pricing, settlement) carries real information.

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 fully carries the return contract: total value, position count, per-position fields (issuer, CUSIP, value, shares, % of portfolio, put/call), cross-sub-manager merge, quarter-over-quarter new/exited/adds/cuts, and a plain-English summary. An agent can predict the response and cost without any further source.

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%, so the baseline is 3; the description still adds some meaning by tying `period` to 'latest or any period', explaining that returned changes compare against the prior quarter, and noting that `limit` affects listing while totals/changes cover the whole portfolio. The manager-name examples largely duplicate the schema, which keeps this from a 5.

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 title and description state a precise verb+resource: 13F-HR fund holdings for a named manager or CIK, with concrete example questions ('What does Warren Buffett own?', 'Did Bridgewater sell Nvidia?'). This is clearly separable from siblings like sec_insider_trades or sec_financials, which cover different filer types and 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?

Usage context is clear: give a fund/investor name or CIK, with an enumerated set of common managers and a fallback ('any other 13F filer'). It also sets the eligibility boundary (managers over $100M in US equities file within 45 days), which implicitly tells the agent when this tool applies. It does not, however, name a sibling to use instead for adjacent questions (e.g., individual insider trades), so no explicit exclusions.

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