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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds an interpretive framing (conviction signal) plus the cluster criteria, but says nothing about result ordering, caps, or return shape.

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?

Two tight sentences with the screening criteria front-loaded and no repetition of the title or schema. The second sentence is interpretive rather than informational, which slightly dilutes it but still earns its place as the rationale.

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 three-parameter screener with full schema coverage and a complete annotation set, the description is nearly sufficient. With no output schema, a brief note on what is returned (issuer list with insider/value counts) would close the remaining gap.

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% and every parameter carries its own default, max, and minimum constraints, so the schema does the heavy lifting. The description adds no syntax or semantics beyond what is already structured, making the baseline 3 correct.

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 signal and its criteria: companies with multiple distinct insiders buying open-market stock within a window. An agent can tell what the tool screens for. However, it never names its obvious counterpart cluster_sells, so the differentiation from the sibling is left to the name alone.

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?

"Strong conviction signal" implies when the tool is useful (bullish insider-conviction screening), which is real but indirect guidance. There is no explicit when-not or named alternative such as cluster_sells or company_insider_pulse.

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