Insider-buy signals in a date range

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

With no annotations, the description carries the behavioral burden and does well: it discloses the default limit of 25, pagination via offset, the total_matched count, and the filing_url on each record. It does not cover error behavior or the interaction between days and start/end, but the core query behavior is transparent.

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 dense, well-structured sentences that front-load the core purpose and then compactly cover defaults, pagination, filtering, and response context. There is no filler or redundant repetition of schema details.

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 query tool with no output schema and no annotations, this description is largely complete: it explains default behavior, pagination, full count, and a key response field. Minor gaps include the undefined meaning of 'Rule-2' and the ambiguous interplay of days with start/end, but these do not block 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?

Schema coverage is 100%, and each parameter already has a meaningful description. The tool description restates limit/offset/days/ticker behavior and mentions total_matched, but adds little semantic meaning beyond what the input schema already provides.

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 states a specific verb ('Returns'), a concrete resource ('Rule-2 insider-buy signals'), and a clear scope (filed within an inclusive ISO date range). This distinguishes it from siblings like insider_signals_by_ticker and insider_signals_today.

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 date-range focus is clear, and optional filters like ticker and days signal when this tool is appropriate. It does not explicitly name alternatives or exclusion criteria, but the context is strong enough for an agent to select it for date-based insider-buy signal queries.

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