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

With no annotations, the description carries full burden. It states returns recent filings and filtering, but does not disclose read-only nature, rate limits, pagination behavior, or what happens on no results. Adequate but lacks depth.

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 tight sentences: first defines purpose and output, second gives usage guidance. No redundant words, all earn their place.

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?

Lacks output schema and does not describe return format. With sibling tools, the context is partially inferred, but for a search tool, the missing structure is a gap. Otherwise covers key filtering details.

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 baseline is 3. The description adds little beyond what the schema provides (e.g., 'provide either ticker OR cik' is already in schema descriptions). No substantial added meaning.

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 verb (search), resource (SEC EDGAR filings), and scope (US-listed company, filtered by ticker/CIK, form type, date range). It is distinct from siblings like edgar_read_filing and edgar_get_8k, which retrieve specific filings.

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 says 'Use this when the user asks "what did <company> file" or needs to find a specific filing.' It provides clear context but does not explicitly mention when not to use it or name alternatives, though siblings are available.

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