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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds the mechanism (EFTS index) but does not disclose pagination/result-cap behavior beyond the schema's limit field or note any rate limit, so it adds only modest context.

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?

Three tight sentences, front-loaded with the core capability and with no filler. The final 'useful for' sentence is mild restatement but still informative; overall efficient.

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, non-destructive search tool with 5 fully documented params and no output schema, the description covers what the tool does and the filter dimensions. It omits no critical call-time information, though alternatives/routing and result-shape hints would make it complete.

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 all five parameters are already documented in the schema. The description restates form-type and date-range filtering but adds no syntax, format, or edge-case detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb+resource ('full-text search across all SEC filings via the EDGAR EFTS index'), which is precise enough to distinguish it from listing tools like edgar_filings_by_form_type or edgar_recent_filings. It does not explicitly name a sibling to differentiate against, so it stops short of a 5.

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' gives a clear intended context, but there is no guidance on when NOT to use it versus alternatives (e.g. edgar_filing_content for a single known filing, or edgar_filings_by_form_type for form-based listing). Usage is implied rather than directed.

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