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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description need not repeat that. It adds behavioral context by asserting the data is 'authentic' SEC EDGAR statutory data, specifying the forms, and noting that returned accession numbers are 'recent' rather than a full history. No contradiction with 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?

Two sentences with no filler; the first sentence front-loads the core action and scope, and the second lists output highlights. The parenthetical '<1.5 KB' is slightly cryptic and the phrase 'Retrieves ... filings' is loose because the tool actually returns metadata/accession numbers, but overall the definition is compact.

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 read-only retrieval tool with 100% schema coverage, an output schema, and rich annotations, the description is nearly complete: it gives jurisdiction, accepted identifiers, form types, and a sense of the returned fields. The only minor gap is ambiguity about whether it returns full filing text vs. metadata, and the meaning of '<1.5 KB' is unexplained.

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 documents identifier, forceFresh, and maxAgeHours fully, including spend-control behavior. The description's 'by stock ticker symbol or 10-digit CIK' merely echoes the identifier property and adds no new parameter-level detail.

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 states a specific verb ('Retrieves') with a precise resource ('US SEC EDGAR statutory filings'), and enumerates the forms covered (10-K, 10-Q, 8-K). It also names the input as ticker or 10-digit CIK, which clearly separates it from siblings like get_uk_company_filing and get_eu_public_tender.

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 establishes clear jurisdictional context ('US SEC EDGAR') that tells an agent when to select this tool over UK/EU/French filing tools, but it does not explicitly state when not to use it or name an alternative. Sibling names provide enough contrast, so this is clear context without formal exclusions.

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