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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the EFTS index context but discloses no additional behavioral traits beyond that — no rate limits, date coverage limitations, or result format expectations.

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, zero filler. The core operation and scope are front-loaded in the first sentence, and the second sentence earns its place by clarifying the typical use case. Every word contributes.

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?

For a read-only search tool with fully documented parameters and strong annotations, the definition is mostly adequate. The main gap is that with no output schema, the description offers no hint about what the agent will receive back (e.g., matching filing metadata or excerpts), leaving a moderate blind spot.

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 description coverage is 100%, so the schema already documents all five parameters. The description's mention of 'comma-separated form types and date range' mirrors existing schema text and adds no new semantic meaning, keeping this at the baseline 3.

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 names a specific verb and resource ('Full-text search across all SEC filings via the EDGAR EFTS index'), which clearly identifies what the tool does. The 'full-text search' angle and 'all SEC filings' scope implicitly distinguish it from siblings like edgar_filings_by_form_type and edgar_recent_filings, but it does not explicitly name or contrast any sibling.

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?

'Useful for finding filings that mention specific terms' provides clear, direct guidance on when to use this tool. However, it offers no exclusions or pointers to alternatives among the EDGAR siblings (e.g., when to reach for edgar_filing_content instead of this tool).

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