Insider Transactions (Forms 4/5)

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

With readOnlyHint=true already covering safety, the description adds substantial context: Form 3 vs Form 4/5 scope, the meaning of each Type code, the 10b5-1 column ('-' means pre-2023 filing), and that Owned After is restated onto today's split basis. It does not cover auth requirements or rate limits, but for a read tool it discloses a lot beyond annotations.

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?

It is dense but front-loaded, leading with purpose, then scope exclusions, then column semantics, then filters. Every sentence carries information, though the column-by-column explanation is long enough to sacrifice some scannability.

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?

There is no output schema, so the description must explain return columns, and it does: Type, 10b5-1, Shares/Price/Value, and Owned After. Combined with the fully documented input schema, an agent has everything needed to call and interpret this tool.

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 100%, so the baseline is 3, but the description adds real meaning by explicating the transactionType values ('Buy'/'Sell' are open-market only versus compensation/derivative mechanics) and matching the descriptive filters (date-range, transaction-type, insider-name) to their parameters. The insiderName multi-word matching nuance is left to the schema.

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 and resource ('Get recent insider trading transactions for a stock') and names its source (SEC Forms 4 and 5) and ordering ('newest first'). It also excludes Form 3 by explaining it covers initial ownership, not transactions. It stops short of distinguishing itself from sibling tools like GetInsiderOwnership or SearchInsiders.

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?

Usage context is implied by the trailing 'Use this to understand insider buying/selling activity' and by the filter list, but there is no explicit when-to-use/when-not guidance or named alternative among siblings like GetInsiderOwnership or SearchInsiders. The interpretation guidance is helpful but does not route the agent between tools.

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