Insider-buy signals for a ticker

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

With no annotations, the description carries the behavioral burden, and it discloses the default limit of 25 newest-first, pagination via offset, optional days filtering, the total_matched count behavior, and filing_url on each record. It could add details about invalid-ticker handling or what Rule-2 means, but the main behavioral surface is covered.

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 compact and front-loaded: scope first, then defaults and pagination, then response highlights. Every clause adds operational value and there is no filler.

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 simple one-required-parameter listing endpoint, the description is complete: it explains the default behavior, how to paginate, the optional time filter, the full count field, and the source URL on each record. Nothing an agent needs to call it correctly is missing.

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?

All four parameters are already documented in the schema (100% coverage), so the baseline is 3. The description mostly restates the schema's default, pagination, and days behavior without adding genuinely new semantics.

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 opening phrase 'All Rule-2 insider-buy signals for one ticker' names a specific resource and scope, and the title reinforces the ticker focus. The case-insensitive note and pagination details make the tool's job unambiguous and distinguish it from date-range or cluster siblings.

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 clearly states that the tool is scoped to a single ticker and explains how to page and filter, so an agent can infer when it is the right choice for a known-ticker signal query. It does not explicitly name alternatives or say when not to use it, but the ticker scope implicitly separates it from insider_signals_by_date_range and insider_signals_today.

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