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

Annotations already declare the safe read-only, idempotent, open-world profile, so the description's job is to add context — and it does: it discloses sort order, the default inclusion of non-material Item 8.01 reports, and the exact fields returned per filing. It stops short of stating pagination or result-count behavior, which keeps it off a 5.

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?

A single dense but well-ordered sentence: resource, sort order, item semantics, then the returned field list. Nothing is repeated and every clause carries information the agent cannot get from the schema.

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?

With no output schema, enumerating the returned fields (company, tickers, dates, items, state, industry code, EDGAR link) is exactly the right compensation, and the 90-day default plus the 2023-12-18 Item 1.05 start date are covered by the schema. Only pagination/total-count behavior is left unstated for this five-parameter list 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 coverage is 80% and the schema already documents query, since, until and material_only. The description adds real meaning by explaining the Item 1.05 vs 8.01 distinction that material_only operates on ('unless excluded'), so an agent understands what filtering that boolean actually removes.

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 resource (cybersecurity incidents on SEC Form 8-K), the item types covered (Item 1.05 and Item 8.01), and the ordering (newest first). It is clearly distinguishable from the advisory/CVE siblings, which cover a different corpus entirely.

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 implies use ('incidents public companies report') and hints that Item 8.01 filings are included 'unless excluded', which points at the material_only filter, but it never states when to prefer this over siblings like list_cyber_advisories or search_federal_register, and gives no exclusions or prerequisites.

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