Get Insider Transactions

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

Annotations already declare readOnlyHint=true, so the tool is known safe. The description adds behavioral context by describing the returned data type and filter capabilities, but does not mention rate limits or other operational constraints, which is acceptable given the annotation coverage.

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 with 4 sentences, each earning its place: purpose, return data, pagination, filtering, and use case. Information is front-loaded, and no redundant or irrelevant content exists.

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?

Given the presence of an output schema (so return values need not be described), the description covers all essential aspects: filtering, pagination, transaction codes, and a practical pattern. No gaps are evident for a tool of this complexity.

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% with descriptions for all 6 parameters. The description adds value beyond the schema by listing example transaction codes and explaining how to use year/month filtering. It does not repeat schema information verbatim.

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 clearly states it retrieves insider transaction history from Form 4 filings, specifying the data fields returned (insider name, title, shares, price, transaction codes). It distinguishes from siblings implicitly by focusing on transaction-level detail rather than positions or clusters, but does not explicitly differentiate.

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 explicit filtering guidance (year, month, transactionCode) and a practical use case ('first insider buy since X patterns'). However, it does not directly state when to use this tool over alternatives like get_insider_positions or get_insider_cluster_buys.

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