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

The description adds meaningful behavioral context beyond the annotations: it discloses the data source (SEC Form 4), the types of transactions included, and the possible signal values. This is consistent with the readOnlyHint, openWorldHint, idempotentHint, and destructiveHint annotations; no contradiction exists.

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 description is a single dense sentence that front-loads the core purpose and uses a compact list for outputs. Every element earns its place, and the signal enum adds practical value without fluff.

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?

Without an output schema, the description carries a heavy burden for explaining return values; it does list key components and signal categories, which is helpful. But it omits the role of the `days` parameter in shaping the output and does not explain how the signal is derived or how results are structured, leaving meaningful gaps for a complex data tool.

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?

The schema describes `symbol` but not `days`; the tool description only hints at recency through 'recent transactions' without explaining the `days` parameter, its default, or its effect on results. With schema description coverage at only 50%, the description does not compensate for the missing parameter meaning.

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 clearly names a specific resource (SEC Form 4 insider trades) and enumerates concrete outputs such as open-market purchases/sales, 10b5-1 plans, per-insider totals, and a signal. It is unambiguous about the tool's domain but does not explicitly differentiate it from related siblings like get_smart_money or get_symbol_intelligence.

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 intended use case is implied by the domain: if you need SEC Form 4 insider activity, this tool provides it. However, there is no explicit when-to-use guidance, no mention of alternatives, and no statement about when this tool is preferable to a sibling.

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