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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds value beyond those annotations by disclosing the return shape (accession numbers and filing dates) and the limitation that this tool does not provide detailed transaction data. This is meaningful behavioral context, though it does not mention ordering or recency windows.

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 filler. The primary action and return content are front-loaded, and the pointer to edgar_filing_content is placed exactly where the agent needs it.

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 a simple two-parameter tool with no output schema, the description covers the essential purposes: what it lists, what it returns, and where to go for more detail. It could add a bit more about recency or ordering, but it is sufficiently complete for correct tool selection and invocation.

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 both parameters are already documented in the schema. The description does not add parameter-level meaning beyond clarifying that the tool targets a company's Form 4 filings, which is the baseline expectation given full schema coverage.

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 opens with a specific verb and resource: 'List recent Form 4 insider transaction filings for a company.' It also states the return scope (accession numbers and filing dates) and explicitly differentiates itself from edgar_filing_content, which is the natural sibling for detailed transaction data.

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 when-not guidance: this tool lists filings, not transaction details, and directs the agent to 'use edgar_filing_content on each' when detailed data is needed. This explicitly routes the agent to the correct alternative.

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