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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds valuable context: the data source (Form 4 filings), the need to distinguish transaction codes, and the important coverage limitation. It does not mention rate limits, auth, error behavior for untracked tickers, or pagination, but the caveats provided are substantive and go beyond a generic data-fetch description.

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 compact yet information-dense: it opens with the core purpose, then covers returned fields, intended usage, a critical interpretive warning about transaction codes, and a coverage caveat. Every sentence adds meaningful information, and the structure is logical and easy to scan.

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 description is reasonably complete for a data-retrieval tool: it lists the returned fields, explains why transaction-code interpretation matters, and notes coverage limitations. However, without an output schema or annotations, it should also clarify how the days and limit parameters affect results, what happens for untracked tickers, and how this tool compares to similar insider-trade siblings.

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 33% (only ticker has a description). The description adds meaning only for the ticker parameter by warning that coverage is limited to a tracked issuer set; it offers no guidance for the days or limit parameters, which have no schema descriptions beyond their numeric bounds. Given the low schema coverage, the description fails to compensate for the majority of parameters.

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 identifies the tool's resource ('Insider transactions straight from the Form 4 filings') and lists the specific fields returned (owner, title, transaction code, direction, shares, price, shares held after). It also distinguishes itself from broader market tools by noting it covers a tracked issuer set, not the whole market, and names its intended use case ('insider conviction around events').

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?

It explicitly says when to call it ('for insider conviction around events') and gives a when-not caveat ('Coverage is a tracked issuer set, not the whole market'). It also provides interpretive guidance on transaction codes (P/S vs M/A), but it does not name alternative sibling tools or explain why this one should be chosen over similar insider-data tools.

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