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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the upstream source (Form 4), that open-market buys and sales are summed/aggregated, that filings are linked to the SEC, and that 10b5-1 plan status is surfaced. It does not mention latency, rate limits, or what happens when a company has no filings, which would be needed for a 5.

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?

One dense, front-loaded paragraph that opens with the core question (what insiders bought and sold) before piling on the field list. The long enumeration of trade types and output fields is informative but slightly list-heavy. Nothing is truly redundant, so 4 rather than 5.

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 present, the description takes on the job of describing return values and does so thoroughly: per-filing fields, aggregated open-market totals, and SEC links. For a two-parameter read-only lookup, an agent has everything needed to call it and interpret the result.

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% — the schema itself documents that 'company' accepts a ticker, name, or CIK, and that 'limit' defaults to 10 with a max of 20. The description adds nothing about either parameter (no guidance on name-vs-ticker reliability or on how limit interacts with the aggregation). Baseline 3 applies since the schema carries the parameter burden.

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 names the resource precisely — Form 4 insider transactions from SEC filings — and enumerates exactly what is returned (who, when, trade type, shares, price, value, holdings after, 10b5-1 flag). An agent can immediately tell this is the insider-trading tool rather than a general filing or financials tool. It stops short of explicitly contrasting with adjacent siblings such as filing_search or stock_report, which keeps it at 4.

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?

Concrete usage examples are given in quoted natural-language phrasings ('are insiders selling X?', 'did the CEO buy?'), which is unusually actionable routing guidance. There is no statement of when *not* to use it or which tool to prefer for adjacent needs (e.g., raw filing retrieval vs. aggregated trades), so it falls short of a 5.

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