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

Annotations already cover the safety profile (readOnly, idempotent, openWorld=false, non-destructive), so the bar is lower. The description still adds real value beyond them: data provenance (9,453 director transaction records), the cross-referencing methodology, the 30/60/90-day windows, and the output fields (signal type, severity, volume anomaly, director activity). It does not note rate limits or data freshness, keeping it from a 5.

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?

Three sentences, front-loaded with the core purpose, then method/data, then use cases. Every sentence carries weight, though the final clause ('insider confidence signals, potential information leakage, or dilution concerns') slightly overlaps and could be tightened.

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 read-only analytical tool with a full schema and an output schema present, the description supplies enough: what it detects, how, over what windows, and what it returns. Nothing an agent needs to select or invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents ticker, days (30/60/90, default 90), and deal_type. The description only echoes the 30/60/90-day framing already in the schema and adds no syntax or edge-case guidance (e.g. how 'all' interacts with deal_type). 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?

States a specific verb (detect) and resource (insider trading patterns around deals), plus the concrete method (cross-referencing director transactions with deal announcements). This clearly separates it from siblings like get_insider_trades or get_insider_clusters, which surface raw holdings rather than pre-deal signals.

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?

Explicitly lists use cases: insider confidence signals, potential information leakage, dilution concerns ahead of deals. That gives clear when-to-use context, but it never names an alternative tool (e.g. get_insider_trades, get_deal_prediction) or a when-not-to-use condition, so it stops short of a 5.

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