get_insider_transactions

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It adds value by explaining the tool returns individual transactions, total sales/purchases in dollars, a Net Insider Sentiment score, and detects 10b5-1 scheduled sales without exempting them. This goes beyond the schema and provides useful behavioral context, though it omits potential rate limits or authorization requirements.

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 three sentences, each earning its place: first states purpose, second outlines outputs, third adds behavioral nuance. No superfluous information, clearly structured and front-loaded with the action.

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 tool with two simple parameters, no output schema, and moderate complexity, the description covers purpose, outputs, and a key behavioral detail (10b5-1 handling). It could mention authorization requirements or rate limits, but overall it is sufficiently complete for effective use.

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 coverage is 100%, so the input schema already documents both parameters. The description mentions 'ticker' and 'windowDays' in context but does not add new syntactic detail beyond what the schema provides. The baseline of 3 is appropriate as there is marginal added value.

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 'Get insider Form 4 transactions for a ticker over the last N days.' It specifies a concrete verb ('Get'), resource ('insider Form 4 transactions'), and scope ('ticker', 'N days'). This distinguishes it from siblings like 'get_sec_filings' or 'get_market_data'.

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 usage for analyzing insider transactions and mentions detection of 10b5-1 sales, but it does not explicitly state when to use this tool versus alternatives like 'get_sec_filings' which may also contain insider data. No 'when not to use' guidance is provided.

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