get_insider_trades

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

With no annotations provided, the description discloses key behavioral traits: default aggregation ('rows are aggregated transaction events... same-day 10b5-1 tranches collapsed'), the flat=True option for per-slice rows, and ticker resolution ('historical ticker resolves to META'). This adds value beyond the schema, though it does not mention rate limits, auth, or other side effects.

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 reasonably concise and front-loaded with the core purpose. The 'Args:' block is slightly redundant because it duplicates ticker details already covered in the prose, but the overall structure is clear and not overly verbose.

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?

Considering 7 parameters, no annotations, and the presence of an output schema, the description covers the essential use cases: ticker scoping, filtering options, and default aggregation behavior. The lack of detail on 'limit' and transaction type values is a minor gap, but the description remains sufficiently complete for effective tool selection and invocation.

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 0%, so the description must compensate. It thoroughly explains ticker (including CIK, stripped CIK, historical ticker), explains flat=True, and mentions filtering by type, min_value, and date range. However, it omits the 'limit' parameter and does not specify allowed values or formats for 'type', 'min_value', or date range, leaving important gaps.

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 opens with 'Get insider trading transactions (Form 4)' and lists transaction types (purchases, sales, grants, option exercises), clearly defining the tool's scope. This distinguishes it from sibling tools like get_executive_compensation or search_filings by focusing specifically on Form 4 insider trades.

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 advises 'Use ticker to scope to one company, or omit to search across all companies' and mentions filtering by transaction type, minimum value, and date range, providing clear contextual guidance. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of a full 5.

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