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

Annotations already declare readOnlyHint and idempotentHint, so the description adds valuable domain-specific context: the data represents proposed, not yet executed, sales and includes broker and approximate sale date. This goes beyond the safety annotations and helps the agent understand the nature of the results. No contradiction with 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 only two sentences and every clause earns its place: the SEC form type, the proposed nature, the before-execution timing, the leading-indicator framing, and the included fields. It is dense but immediately readable, with no redundant phrases.

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 search tool with 7 parameters but no output schema, the description provides the essential conceptual model (Form 144 vs Form 4) and a practical use case ('leading indicator'). It also mentions the return components (broker, approximate sale date). It doesn't enumerate all possible filters, but the schema already covers them, so the description is sufficiently complete for correct tool selection.

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 all seven parameters are fully documented in the schema. The description does implicitly connect the 'approximate sale date' language to the since/until parameters, but it doesn't introduce any new parameter semantics beyond what the schema already provides. The baseline of 3 is appropriate since the schema carries the burden.

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 the specific verb 'Search' and names the exact resource ('SEC Form 144 notices'). It clearly distinguishes this tool from siblings like get_insider_trades by explaining that these are proposed sales filed before execution, whereas Form 4 reports execution afterward. This makes the purpose immediate and unambiguous.

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 provides clear usage context by explaining the proposed-sale timing and labeling the data as a 'leading indicator.' It implicitly tells the user when to choose this tool over executed-sale tools, but it doesn't explicitly name alternative sibling tools or list exclusions. The context alone is enough to infer appropriate usage.

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