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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only describes the scope (full-text, all filings) and lists forms, but does not mention that this is a read-only operation, rate limits, result ordering, or any side effects. The irrelevant '4,000+ stablecoin results' adds confusion rather than transparency.

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?

The description is only two sentences and front-loaded with the main purpose. However, the second sentence contains '4,000+ stablecoin results,' which is irrelevant to the tool's general function and wastes space, potentially misleading users. It should be removed or replaced with more useful context.

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 simple search tool with 2 well-documented parameters and no output schema, the description covers the basic scope. However, it lacks any comparison to sibling tools (especially sec_company_filings), omits expectations about result format, and includes an odd stablecoin stat that introduces ambiguity.

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% (both 'query' and 'limit' have clear descriptions). The description adds no new parameter-level meaning beyond the schema; 'full-text search' already implies the query is a text term. Thus 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 performs 'Full-text search across all SEC EDGAR filings' and lists specific form types (10-K, 8-K, S-1, CORRESP). This is a specific verb+resource that distinguishes it from more general search tools, though not explicitly from the sibling sec_company_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?

The intended use is implied: use for full-text search across all SEC EDGAR filings. However, there is no explicit guidance about when to use this tool versus alternatives like sec_company_filings, nor any exclusions or prerequisites. The form-type coverage provides some context but no direct comparison to siblings.

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