Get insider trades

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds the return structure (data + summary) and mentions a bullish signal for cluster buying. It doesn't address pagination, exact field names, or time ranges, but the annotations lower the burden.

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 two sentences, front-loaded with the main function and output summary, followed by a useful interpretation note. Every sentence adds value with no redundant 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?

The description covers purpose, output structure, and a usage signal, which is adequate for a simple read-only tool. However, it doesn't mention what 'recent' means (time range) or distinguish from overlapping insider tools, leaving a small but notable 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?

With 0% schema description coverage, the description should compensate by explaining the 'ticker' parameter. It merely says 'for a ticker' and doesn't add details about format, examples, or possible values. The parameter name is self-explanatory, but the description contributes little beyond the schema.

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 recent Form 4 transactions and a summary with net buy/sell counts and dollar value, which is a specific verb+resource. It doesn't explicitly differentiate from sibling tools like stoquant_get_insider_cluster or stoquant_get_big_insider_buys, but the core purpose is unambiguous.

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 provides a clear usage directive: 'Use to check whether insiders are accumulating or distributing.' This gives contextual guidance without explicit exclusions or references to alternatives, but the context is clear enough for an agent to decide when to invoke this tool.

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