Get insider trades (Form 4)

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

Annotations already cover the read-only, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds useful context by specifying the parsed source (Form 4 filings), the output summary, and the meaning of transaction codes—value beyond the annotations. It does not mention rate limits or failure modes, but for a read-only EDGAR tool that is a minor gap.

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?

The description is compact and front-loaded: the first sentence states the verb, resource, scope, and output fields; the second sentence efficiently maps transaction codes. Every sentence earns its place and there is no filler.

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 read-only tool with no output schema, the description does a good job enumerating return values and the output summary, while the schema covers parameter semantics. It does not precisely define 'recent' or explain pagination/limits, but given the openWorldHint and the simplicity of the tool, this is not a serious gap.

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 all four parameters. The description adds value by explaining transaction codes like P, S, A, and F, which supports understanding of open_market_only, but it adds no syntax or format details beyond what the schema already provides.

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 uses a specific verb ('Get') and resource ('insider transactions from Form 4 filings') and enumerates the returned fields, making it clearly distinct from generic EDGAR tools like edgar_list_filings or edgar_read_filing. It also identifies the reporting subjects (officers, directors, 10% owners), which sharpens the purpose.

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 description never says when to choose this tool over alternatives such as edgar_read_filing or edgar_list_filings, nor does it give exclusion criteria. Usage context is only implied by the phrase 'recent insider transactions'; there is no explicit when/when-not guidance.

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