Insider trades (Form 4)

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description still adds real context beyond them: it discloses the XML source, the inclusion of Form 4/A, and — most usefully — that `limit` counts filings rather than transactions, which the annotations do not express.

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?

Purpose is front-loaded and every clause carries information, with the caveat about `limit` counting filings placed as a useful trailing clarification. The long field enumeration is dense but justified since there is no output schema to carry it.

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 thoroughly compensates by enumerating the returned fields and the buy/sell summary, and the parameters are well documented. What is missing is guidance on when to choose this tool versus assembling insider data from other filing tools, and any pagination/volume behavior.

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 86%, so the schema already documents most parameters and a baseline of 3 applies. The description nonetheless adds meaning beyond the schema by spelling out the plain-English meaning of the transaction codes (P/S/A/M/F/G), which the schema only gestures at with an example.

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 a precise verb+resource ('Recent insider transactions for a company (issuer)') and pins the exact source (SEC Form 4 / 4/A XML). It enumerates the returned fields, making the tool's scope unmistakable and clearly distinct from every sibling in the list.

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 is only implied — the tool is obviously the direct path for insider trades, but the description never states when to prefer it over siblings like list_filings plus get_filing_document, nor any prerequisites. The one routing hint ('use search_company first if unsure') lives in the schema, not the description.

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