get_insider_transactions

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

No annotations are present, so the description must carry the behavioral burden. It states what data is covered (buy/sell transactions) but does not disclose ordering, time range, pagination, return format, or whether the response includes transaction dates, prices, or share counts. Without annotations, this is a material 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 one concise, front-loaded sentence with no redundancies. Every word earns its place.

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?

With no output schema and no annotations, the description should provide some detail about the returned data shape or response characteristics. It only says 'insider buy/sell transactions', leaving the agent to guess whether this returns a list, a summary, or detailed trade records. The limited parameter set keeps it from being a 1, but it is not fully callable with confidence from the description alone.

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?

The description adds no parameter-level meaning. The input schema already documents 'symbol' with a ticker example and gives numeric constraints for 'limit', so the description contributes nothing beyond the schema. With schema_description_coverage at 50%, the 'limit' parameter remains unexplained in prose.

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 a distinct resource ('insider (officer/director) buy/sell transactions'), clearly identifying the data scope. It effectively distinguishes from sibling tools like get_holders, get_fund_holders, and get_company_events, none of which cover 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?

There is no guidance on when to use this tool instead of alternatives such as get_holders, get_company_events, or get_fund_holders. The description implies a use case for insider transactions, but it never states exclusions, prerequisites, or conditions that should route an agent to a sibling.

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