search_insider_transactions

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

With no annotations provided, the description alone must convey behavioral traits. It only states that it searches, implying a read-only operation, but fails to disclose pagination behavior (despite cursor and limit parameters), the scope of results (e.g., whether it returns both derivative and non-derivative trades), or the output format. There is no mention of rate limits, ordering, or any constraints. The single sentence provides minimal behavioral insight beyond the verb 'Search'.

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 a single, front-loaded sentence with no filler. It immediately states the action, the subject matter, and the major filtering dimensions. Every word contributes to surface-level understanding, making it highly concise and well-structured.

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 13 parameters, no output schema, and no annotations, making the description the only source of guidance. It fails to mention pagination (despite cursor/limit params), result shape, default behaviors, or relationships to other tools like get_insider_filing. For a search tool of this complexity, the one-line description is insufficient for an agent to invoke it correctly without additional inference.

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 only 38%, so the description must compensate. It does add domain context by specifying the SEC form types (3/4/5) and names the main filter categories (issuer, owner, transaction code, date, value). However, it does not clarify all 13 parameters, resolve ambiguities like issuer vs. issuer_cik, or explain date formats or the meaning of value (min_value_usd). This partial compensation earns a medium score.

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 uses a specific verb ('Search'), specifies the exact resource ('Form 3/4/5 insider transactions'), and lists the key search dimensions (issuer, owner, transaction code, date, and value). This clearly distinguishes it from sibling tools like get_insider_filing (which retrieves a single filing) and search_filings (general SEC filings), making the purpose unmistakable.

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 clear context for when to use this tool: when searching insider transaction filings by the listed criteria. It does not explicitly mention alternatives or when NOT to use it, but the strong domain framing ('Form 3/4/5 insider transactions') implicitly sets it apart from other search tools. No exclusions or alternative references are given, but the intended use case is evident.

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