Search SEC Filings

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

The description states it returns paginated results with metadata, which aligns with the readOnlyHint annotation. No contradictions. It adds value by explaining the paginated nature and the metadata fields, though it doesn't detail other behavioral aspects like rate limits.

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: first states purpose and filters, second explains usage flow. Every sentence serves a clear function, no fluff. Front-loaded with the most important information.

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 6 fully described parameters, an output schema, and readOnlyHint annotation, the description covers the essential flow: search, filter, paginate, then read with other tools. No significant gaps.

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 100%, so the description does not need to add much. It mentions CIK, form type, and date range, which mirror schema descriptions. No additional meaning beyond what's in the schema, so baseline 3 is appropriate.

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 searches and lists SEC filings with specific filters (CIK, form type, date range). It distinguishes from sibling tools like get_filing_document and get_filing_exhibits by noting the use case of finding filings before reading content.

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?

Explicitly tells when to use this tool: 'Use this to find filings before reading their content with get_filing_document or get_filing_exhibits.' This provides clear context and names alternatives.

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