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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond that: it explains the filing timing (before execution), the regulatory source (SEC Form 144), and the interpretation as a leading indicator. This is substantive and helps the agent understand what the data represents without contradicting annotations.

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 two sentences with no filler. The core action and key differentiator ('filed BEFORE the sale executes') are front-loaded, and the leading-indicator framing adds value without redundancy. Every sentence earns its place.

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 read-only search tool with 7 optional, well-documented parameters and no output schema, the description covers the domain concept and expected output hints (broker, approximate sale date). It does not explain pagination or return shape, but the schema documents the cursor and the annotations cover safety. Minor gaps remain around result ordering and field availability, but overall it is complete enough for correct invocation.

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 input schema already provides full descriptions for all 7 parameters (100% coverage), including the approximate sale date semantics for 'since' and 'until.' The description does not add additional parameter-specific details beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Search SEC Form 144 notices') and identifies the exact resource and filing type. It clearly distinguishes this tool from Form 4-based insider trade tools by emphasizing 'PROPOSED sales... filed BEFORE the sale executes' and calling it a 'leading indicator.' This is unambiguous and differentiated from siblings like get_insider_trades.

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 description gives clear context for when to use this tool: for announced-but-not-yet-executed insider selling, as opposed to Form 4 execution data. It does not explicitly name alternative sibling tools, but the contrast with Form 4 implicitly guides the agent away from executed-trade tools. No explicit when-not-to-use list is provided, so it stops short of a 5.

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