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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal useful traits: data available since 2020, up to 2,000 rows, and the two modes. But it omits important behaviors such as what happens with no parameters, how 'latest' is defined, whether results are sorted, and what the response structure looks like.

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 at two sentences, and the key output details are front-loaded. However, the second sentence is a long run-on that mixes the two modes into one clause; breaking it into separate sentences or bullets would improve scannability.

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?

The tool has 6 parameters, 0 required, no output schema, and two distinct modes. The description fails to cover the window parameter entirely, does not explain parameter interactions (e.g., can ticker be combined with type?), and does not state defaults when no arguments are supplied. This leaves significant gaps for an agent deciding how to call the tool 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 description coverage is 83%, so the baseline is 3. The description adds minimal beyond the schema: it groups from/to/limit as 'select the window' and explains type P/S, but the schema already conveys most of that. Critically, the window parameter is not mentioned in the description and has no schema description, so the meaning of '7d/30d/90d' remains unexplained.

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 clearly states the tool returns insider transactions from SEC Form 4, lists the specific data fields (insider name/title, transaction code, shares, price, value, date), and distinguishes the two primary modes: ticker history and latest trades across companies. However, it does not explicitly contrast itself with sibling tools such as insider_clusters or planned_insider_sales, so it falls short of full 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?

The description gives clear conditions for using the two modes: from/to/limit for ticker history, and type P/S for latest trades across companies. It does not, however, provide any guidance about when to prefer this tool over sibling alternatives, nor does it state exclusions like 'do not use when tracking planned sales'.

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