filings_insider_trades

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

Beyond the read-only/idempotent annotations, it discloses the default filtering behavior, the pricing model (x402 USDC on Base or API key), and crucially that a bare HTTP 402 carries a price quote rather than being a failure — a behavior an agent would otherwise misread as an error.

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 resource and row shape, then field list, then a worked example, then usage and behavior. The example URL and behavior paragraph are useful rather than padding, though the field enumeration is slightly redundant with the schema.

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 an 11-param, no-output-schema read tool, it covers defaults, scope, alternatives, and payment/auth failure semantics. Return shape isn't described (cursor/pagination lives only in schema), but with annotations and full schema coverage this is close to complete.

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 baseline is 3; the description adds meaning on top by decoding the transaction codes (P/S/A) and restating the open-market default that governs all_codes. It doesn't add much for the cursor/wait long-poll semantics, but that's already fully documented in the schema.

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?

Specific verb+resource: 'Form 4 insider transactions parsed to one row per trade', and it enumerates the per-row fields the agent will get. It explicitly contrasts with filings_insider_summary, so an agent can pick between them without inspecting schemas.

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?

'Use when you want individual Form 4 insider transactions, one row per trade. Not for a per-ticker rollup (use filings_insider_summary)' gives both the selecting condition and the named alternative. It also states the default scope (open-market buys and sells only), which shapes when this tool is appropriate.

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