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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, yet the description still adds real value: it discloses the cost model ('each filing costs one SEC request') tied to the filings parameter, and it explains the return payload shape (summary object plus one row per transaction). It does not mention failure modes such as unknown tickers or CIKs with no Form 4s.

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 scope, then returns, then a usage hint — a sensible ordering with no filler sentences. The long comma-separated field enumeration is dense but every field listed is useful given there is no output 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?

With no output schema, the description carries the burden of describing return values, and it does so thoroughly (summary aggregate fields plus per-transaction fields including the 10b5-1 flag and filing link). Combined with a 100%-covered schema and clear read-only annotations, an agent has everything needed to call it correctly.

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 baseline is 3. The description does add meaning for the codes parameter by expanding the transaction code legend (P/S/A/M/F/G), which goes slightly beyond the schema's bare examples, but that same legend is largely restated ground already implied by the enum and per-parameter descriptions.

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 and resource with scope: 'Recent SEC Form 4 insider transactions for one company (ticker or issuer CIK) or one insider (reporting-owner CIK)'. An agent immediately understands both input modes and the output shape. It does not name or contrast with the sibling get_market_insider_buys, so it stops short of full sibling differentiation.

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?

Only guidance is 'Use side="buy" to see only open-market purchases', which is a parameter-level filter hint rather than when-to-use-this-tool guidance. There is no statement of when to prefer this over get_company_filings or get_market_insider_buys, and no prerequisities or exclusions.

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