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

Goes well beyond the readOnly/idempotent annotations by disclosing the analytical method itself: batch detection is same-day + similar modest amounts signaling a company program, and the 0–100 conviction score is defined by its components (independent buyers, C-suite participation, size, stake growth, multi-day spread, minus batch penalty). An agent knows what the output means and how to interpret it before calling.

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?

Front-loaded with the core action, then the batch caveat, then the score definition, then trigger examples — good ordering. The middle sentence is long and clause-stacked, but essentially every clause carries information.

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?

Six optional parameters, an output schema present, and a description that covers exclusions, methodology, scoring and typical queries. Nothing needed to call it correctly is missing; return shape is deferred to the output schema, which is appropriate.

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 baseline is 3. The description adds real meaning to two parameters that the schema only gestures at: it explains what a 'batch' actually is (for exclude_batches) and what the conviction ranking formula contains (for sort_by='conviction'), which the terse enum description does not.

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 and resource: finds companies where multiple distinct insiders made open-market purchases, and explicitly excludes option exercises, awards and sales. That scoping distinguishes it from the generic sibling find_insider_buying, though no sibling is named outright.

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 'Use for ...' clause gives three concrete trigger phrasings (3+ insiders in 60 days, real vs comp-plan buying, rank by conviction), which maps closely to the parameters. It lacks an explicit 'don't use this when X, use find_insider_buying instead' clause against the many sibling insider tools.

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