get_insider_trades

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

No annotations are provided, so the description carries the disclosure burden. It does state the tool is a read-style operation ('Get') and summarizes the return as 'Recent insider transactions and overall insider sentiment,' but it does not explain how 'recent' is defined, data source limitations, or any rate/access considerations.

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 short and well-organized: a one-line purpose statement followed by clearly labeled Args and Returns sections. There is no filler, and the most important information is front-loaded.

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 single-parameter read tool with an output schema available, the description covers the essential purpose, the required argument, and the high-level return. More detail on the meaning of 'recent' would improve it, but nothing critical is missing given the tool's low complexity.

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 input schema only provides the parameter name and type, while the description adds meaning by defining ticker as 'Stock symbol' and giving concrete examples like 'AAPL' and 'MSFT.' This compensates for the schema's lack of property description, though it is still fairly minimal.

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 a specific verb and resource: 'Get insider trading activity for a stock.' This clearly differentiates it from sibling tools like get_quote or get_technical_indicators, and the Returns line narrows the scope to transactions and sentiment.

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 implies use when insider trading information is needed, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. There is no mention of related tools or exclusions, so guidance is only implicit.

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