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

Annotations already mark the tool as read-only and idempotent, so the description does not need to re-state safety. It adds meaningful context about the cross-feed join mechanics ('joins two feeds through the shared entity graph') and the limitation of raw EDGAR, giving insight into how the tool behaves 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?

The description is two sentences with no wasted words. The first sentence states the core purpose with a concrete example, and the second sentence explains the unique cross-feed advantage. Every word earns its place.

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 6 parameters (all optional) and no output schema. The description clearly explains the input context (material 8-K events and prior insider trades) and the output type (SEC Form 4 transactions), but it does not explicitly state the result structure (e.g., whether it returns event details alongside trades), which would have been helpful given no output schema. Still, it is largely complete for a filtering 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 all six parameters are well-documented in the schema. The description does not add any additional parameter-level semantics; it merely mentions the lookback window concept ('N days BEFORE') which is already captured by the 'days_before' parameter. This meets the baseline for schema-heavy tools.

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 the tool's function: show SEC Form 4 insider transactions before material 8-K events. It provides concrete examples (bankruptcy, restatement, delisting) and distinguishes itself from siblings by explicitly noting it joins two feeds, which raw EDGAR cannot do in one query.

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 gives clear context for when to use this tool (for cross-feed insider-trades-before-events analysis) and implies it is the right choice over raw EDGAR for this specific query. However, it does not explicitly state when NOT to use it or name alternative sibling tools, so it lacks formal exclusions.

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