List SEC filings

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavioral context: newest-first ordering, the exact fields per row, amendment inclusion semantics tied to base-form filtering, and automatic fetching of older history pages for pagination.

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?

Purpose and ordering are front-loaded, followed by compact detail on row contents, amendment behavior, and supported forms. Slightly dense but each sentence carries information; the common-forms list earns its place as enum-free guidance.

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, the description steps in to enumerate the returned fields and describe pagination behavior, so an agent knows both what it gets back and how older results are surfaced. Nothing essential for correct invocation is missing.

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 71%, and the description compensates by explaining form-type filtering, date-range filtering, and the include_amendments behavior (amendments matched to base forms). It also confirms implicit pagination fetching, though limit/offset themselves are left to the schema.

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 (List) and resource (a company's EDGAR filings) with scope (company-level, newest-first) and the primary filtering dimensions. An agent can immediately tell this is the filings-listing tool, distinct from get_filing_document or get_financials.

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 usage through 'filtered by form type and filing-date range' and the common-form list, but never states when to use this versus sibling tools like get_filing_document or get_financials, nor any explicit exclusions. The 'use search_company first if unsure' hint lives in the schema, not here.

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