insider_transactions_by_ticker

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

With no annotations, the description should disclose behavioral traits. It mentions paging over series and format options (json/csv), but omits details like pagination mechanism (offset/limit), rate limits, authentication, or whether the data is real-time or delayed.

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 short but includes a JSON example that is partially redundant. It could be more concise by removing the example and focusing on essential behavior.

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?

With no output schema, the description partially explains the return structure via JSON example. However, it lacks details on pagination behavior, default limit, and edge cases (e.g., empty results).

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 adds no meaning to parameters beyond the schema's own minimal descriptions (e.g., 'YYYY-MM-DD' for dates). The output format is briefly noted but not tied to the 'format' parameter.

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 'Normalized insider transactions' which identifies the resource, but lacks a clear verb like 'get' or 'list'. It is understandable but not precise enough to distinguish from siblings like 'screener_insider_trading'.

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 on when to use this tool vs alternatives such as 'screener_insider_trading' or 'senate_trades_by_ticker'. There is no mention of prerequisites, limitations, or when not to use.

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