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

Annotations already declare this a read-only, idempotent, non-destructive, open-world query, so the safety profile is covered. The description adds real behavioral context beyond that: it defines what constitutes a cluster (2+ distinct insiders, 7-day window, open-market buys) and states which values are adjustable.

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?

A single dense sentence that front-loads the core cluster definition and appends the output contents. It is efficient, though the parenthetical about adjustable knobs is slightly compressed.

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?

With no output schema, the description usefully names the return contents (each insider, total dollars, filing links), and all six optional parameters are fully documented in the schema. An agent has enough to invoke it correctly; missing only explicit sibling routing.

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 every parameter already carries its own range, default, and meaning. The description only reiterates that window, minInsiders, and minValue are adjustable, adding no syntax or interpretation beyond the schema. Baseline 3 applies.

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 states a precise screening rule: companies where 2+ distinct insiders bought on the open market within a 7-day window. That verb+resource+criteria combination clearly distinguishes it from the broad insider_trades sibling, though it never names that sibling explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the alternative insider_trades tool for non-clustered lookups. The criteria imply a use case but the agent must infer it from the description's semantics alone.

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