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

With no annotations provided, the description carries the full behavioral burden. It helpfully discloses what the tool returns and pins down the cluster-buying threshold ('three or more insiders buying'), but says nothing about auth requirements, data recency, rate limits, or whether the window is calendar vs. trading days beyond the schema's default/max.

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 entire opening sentence is duplicated verbatim, wasting half the description with zero added information. The example URL is a genuine asset, but the duplication badly damages front-loading and density.

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 2-parameter read tool with 100% schema coverage and no output schema, the description compensates well by enumerating the returned aggregate fields. Only auth/data-source context is absent, which is a minor gap given the schema already documents both inputs.

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 baseline is 3. The description reinforces the ticker/window scoping ('one ticker over a window') and the example shows both parameters in use, but adds no format or constraint detail beyond the schema (ticker format, behavior at the 90-day cap).

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 names a specific resource and operation ('Insider activity rollup for one ticker over a window') and enumerates the returned aggregates (buy/sell counts, dollar totals, net flow, distinct buyers/sellers, cluster-buying flag, largest trades). This clearly differentiates it from the raw-list sibling filings_insider_trades, though the description 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?

Usage is only implied: 'rollup for one ticker over a window' suggests a summarization use case, and the example URL shows invocation. There is no explicit when-to-use vs. when-to-use-a-different-tool guidance, and no mention of the closely related filings_insider_trades alternative.

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