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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the meaningful semantic point that the data reflects filed intentions rather than executed sales, but says nothing about freshness/lag of Form 144 filings, ranking behavior, or result limits.

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 front-loaded sentence that states the ranking, the source, and the key caveat with no filler. Nothing is repeated from the title or schema.

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 two-parameter read-only listing tool with full schema coverage and annotations covering safety, the description is close to complete. It only leaves unspecified what the returned records contain (beyond being ranked by sale size) and whether results are truncated, though no output schema exists to carry that.

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 'days' (lookback, default 30, max 180) and 'group_by' (issuer vs seller) are fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 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?

States a specific verb and resource ('lists companies by the size of insider sales') and scopes the data source precisely to SEC Form 144. The parenthetical '(filed intentions to sell, not completed trades)' implicitly separates it from completed-trade siblings like cluster_sells, but no sibling is named directly.

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 'planned, not completed trades' clarification implies when this tool applies versus execution-based tools, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the selection rule from the domain framing alone.

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