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

No annotations are provided, so the description carries the full burden. It usefully discloses the default filtering behavior (P and S only unless all_codes=true) and the 10b5-1 dimension, which are real behavioral traits. It says nothing about auth requirements, rate limits, pagination via the since cursor, or the long-poll behavior of wait, leaving meaningful behavioral gaps.

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 entire opening sentence is duplicated verbatim, wasting roughly half the description with zero added information. The useful parts (default scope, example) are present but buried after the redundant copy, hurting front-loading.

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?

For an 11-parameter, all-optional query tool with no annotations and no output schema, the description does compensate somewhat by enumerating the returned fields. However it omits any routing guidance versus the insider_summary sibling and leaves cursor/pagination semantics to the schema, making it only minimally complete.

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 schema already documents all 11 parameters, including defaults and maxes (days max 90, limit max 200, wait max 25). The description adds no parameter-level meaning beyond restating returned fields, and the example URL only illustrates a couple of params. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Form 4 insider transactions parsed to one row per trade') and enumerates the exact columns returned (insider, role, security, code, shares, price, value, shares owned, direct/indirect, 10b5-1). An agent immediately knows what this tool produces. It does not, however, differentiate itself from the sibling filings_insider_summary, which likely covers similar ground.

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 notes the default scope ('Defaults to open-market buys and sells only'), which implies when you'd reach for all_codes or side. But it never names an alternative tool or states when to prefer filings_insider_summary or filings_search over this one, so usage is implied rather than explicit.

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