finance.sec-filings

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the backend API (SEC EDGAR) and return structure, but does not discuss rate limits, data freshness, or idempotency. For a read-only data tool, this is minimally adequate.

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, front-loaded with the tool's purpose and return value. No redundant or irrelevant information. Every sentence adds value.

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?

Given no output schema, the description adequately describes what is returned (company info and filing list with accession numbers, forms, dates, URLs). It also names the data source. For a simple retrieval tool, this is sufficient.

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 descriptions exist for ticker and formType (67% coverage). The tool description does not add additional meaning beyond the schema for the parameters; it restates the ticker purpose. The limit parameter lacks description in schema and tool description, relying on constraints only.

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?

Description clearly states it retrieves recent SEC filings for a US public company by ticker, lists specific forms (10-K, 10-Q, 8-K), and describes the return content (company info and filing details). This distinguishes it from sibling tools like finance.company-facts or finance.insider-trades.

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 for SEC filings but provides no explicit guidance on when to use vs alternatives, prerequisites, or limitations. No mention of when not to use or exclusion criteria.

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