insider_transactions_by_ticker

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

With no annotations, the description carries full responsibility. It mentions 'paging over series' and output formats (JSON/CSV), but does not explain how paging works, the effect of parameters like limit or date filters, or any constraints. This lacks depth for an operation that mutates nothing but likely has pagination nuances.

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 concise and front-loaded with the key purpose. The included JSON and CSV structure is useful given the lack of an output schema, serving as a de facto output specification. It is efficient without redundant 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?

The tool has nested parameters and no output schema, so the description's output structure is valuable. However, it omits how pagination is performed, how limit interacts with series_total, and how date filters work. This leaves gaps for an agent to correctly invoke the tool without additional context.

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 0% and the description does not compensate. It lists ticker and name in the output structure but does not explain input parameters like limit, date_from, or date_to beyond what the schema already provides (e.g., date format). The mention of 'format' in the JSON snippet hints at output format but not parameter 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 description states that it returns 'normalized insider transactions' with paging, which clearly identifies the resource and action. It is distinguishable from siblings like house_trades_by_ticker and senate_trades_by_ticker by the specific domain 'insider transactions' in the name and description, though it doesn't explicitly contrast with them.

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?

No guidance is provided on when to use this tool versus similar ticker-based tools (e.g., house_trades_by_ticker, analyst_ratings_by_ticker). The description only states what it returns, not when it should be preferred over alternatives.

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