Get Insider Trading Intelligence

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

Annotations declare readOnlyHint=true, consistent with read operation. Description adds significant behavioral context: cluster buying detection, entity-centric model, Form 4 cross-referencing, transaction breakdown by SEC code, netSharesSold12m calculation, and isPrimarilyTaxWithholding flag. Exceeds basic annotation coverage.

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?

Description is moderately long but each sentence adds value. Starts with main purpose, then details features and transaction breakdown specifics. Could be slightly more concise but well-organized.

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 complexity of insider data and existence of output schema, description provides comprehensive overview of data content and flags. Covers transaction codes, net shares, tax withholding distinction, and pagination, making it complete for agent decision-making.

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% with descriptions for ticker, limit, and offset. Description mentions pagination via limit/offset but adds no new semantics beyond schema. Baseline 3 is appropriate.

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?

Description clearly states verb 'Get' and resource 'insider trading discovery data' with specific features like cluster buying detection and Form 4 cross-referencing, distinguishing it from sibling tools like get_insider_transactions or get_insider_cluster_buys.

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?

No explicit guidance on when to use this tool versus alternatives such as get_insider_transactions, get_insider_positions, or get_insider_cluster_buys. Agent must infer from feature list.

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