SEC Form 4 insider trades

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

With no annotations, the description must carry the behavioral load. It usefully discloses the return content and the scope difference between ticker-history and cross-company views, but says nothing about limits, freshness, rate limits, or what happens with no parameters supplied.

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?

Two sentences, front-loaded with the resource and payload, with no filler. The field enumeration is slightly list-like but still earns its place by telling the agent what comes back.

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 3-parameter read tool with no output schema, the description adequately covers the returned fields and the two query modes. It is incomplete on the window parameter and on behavioral constraints, and with no annotations the safety/limits picture is thin.

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 67%; the description echoes the P/S meaning (also in the schema) and hints that 'history for a ticker' is a mode, but the window enum (7d/30d/90d) is neither described in the schema nor explained here, leaving a real gap.

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 specific resource ('Insider transactions from SEC Form 4') and enumerates the returned fields, so an agent immediately knows what it fetches. It does not, however, distinguish itself from the close sibling planned_insider_sales, which is a distinct insider-activity tool.

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?

It implies two usage modes ('History for a ticker or the latest trades across companies') and explains the P/S filter, giving the agent operational context. It offers no explicit when-to-use/when-not guidance and never references an alternative tool for related insider data.

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