get_insider_trading

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool gets 'recent' activity, implying time-bound data, but doesn't specify what 'recent' means (e.g., last 30 days), whether it's read-only, requires authentication, has rate limits, or what the output format is. For a data retrieval tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse. Every part of the sentence contributes directly to understanding the tool's function.

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?

Given the tool's complexity (financial data retrieval), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like data recency, error handling, or output structure, leaving gaps for an AI agent to use it effectively. The conciseness comes at the cost of necessary detail.

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 minimal meaning beyond the input schema, which has 100% coverage with clear descriptions for 'symbol' and 'limit'. It implies the tool filters by stock symbol and returns a limited set, but doesn't provide additional context like symbol format examples or limit constraints. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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's purpose: 'Get recent insider trading activity for a stock.' It specifies the verb ('Get') and resource ('insider trading activity'), and distinguishes it from siblings like get_analyst_ratings or get_balance_sheet by focusing on insider trading. However, it doesn't explicitly differentiate from all siblings (e.g., it's clear but not exhaustive in sibling comparison).

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., for investment analysis), or exclusions (e.g., not for real-time data). With many sibling tools for financial data, this lack of usage context is a significant gap.

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