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

Annotations already declare readOnly/openWorld/non-destructive, so those need no restating. The description adds genuinely useful context beyond them: the upstream source (SEC EDGAR), that it works keyless with a small daily allowance, keyed tiers with a 100 calls/month free cap, and a $0.02 USDC x402 pay-per-call path. It also previews the returned fields, though it omits pagination and 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?

Front-loaded with the definition and the payload, then cost/auth, then a disclaimer — a sensible order with no wasted framing. The pricing tier enumeration ('free 100 calls/month, Starter, Pro') is the least essential clause but is short.

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?

For a two-optional-parameter read-only screen with no output schema, this covers what the tool returns (buyers, roles, totals, VWAP), the data origin, and the access/cost model. An agent can decide to call it and interpret the result without opening anything else.

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 schema already documents both parameters fully; baseline 3 applies. The description restates the lookback and buyer-count thresholds in prose ('last N days', 'several distinct insiders') but adds no format or boundary detail beyond the schema, and its 'last N days' phrasing is slightly looser than the schema's 'by filing date'.

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+resource: tickers where several distinct insiders made open-market purchases (Form 4 code P) over a lookback window, plus the payload fields. The 'several distinct insiders' qualifier implicitly separates it from a single-buyer screening tool, but no sibling is named explicitly.

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 screening scenario is clear from the text (cluster of insiders rather than one-off buys), so usage is implied. However, there is no explicit when-to-use/when-not guidance and no routing toward alternatives such as insider_buys; the remaining sentences cover billing, not selection.

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