finance.sec-filings

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

No annotations provided, so description carries full burden. It mentions the data source (SEC EDGAR) but does not disclose behavioral traits like rate limits, data freshness, error handling for invalid tickers, or if 'recent' is ambiguous.

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 efficiently convey purpose, input, output, and data source. No redundant information. Front-loaded with key details.

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?

The description covers the basic function and output structure but lacks usage guidance, behavioral details, and parameter semantics beyond the schema. For a 3-parameter tool with no annotations or output schema, more context would improve completeness.

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?

The description adds minimal value beyond the schema: it reiterates that ticker identifies the company and formType acts as a filter. The schema already provides examples for ticker and constraints for limit. Parameter descriptions are adequate but not enhanced.

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 clearly states the tool retrieves recent SEC filings by stock ticker, lists filing types (10-K, 10-Q, 8-K), and describes output structure (company info, filings with accession numbers, etc.). It is specific and distinguishes from siblings like finance.company-facts.

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 retrieving SEC filings but does not explicitly state when to use this tool over alternatives (e.g., finance.insider-trades, finance.thirteen-f). No guidance on when not to use it or prerequisites.

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