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

With no annotations, the description carries the full load and does well: it discloses fair-access rate limiting, normalization of hits, the fact that upstream returns no text excerpt so snippets describe the matched document, and the x402 pricing/HTTP surface. It does not state pagination or ordering behavior, keeping it short of a 5.

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 tightly-packed sentences with the core purpose front-loaded and operational metadata confined to a trailing bracket. No filler, though the bracket block is dense with pricing/endpoint detail that dilutes slightly.

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?

No output schema or annotations exist, so the description must cover return shape — and it does, naming company, form, filing date, matched document, and archive URL, plus the snippet caveat. Missing date-filter semantics and any cap on the 20-result limit keep it from a 5.

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?

At 33% schema description coverage over 6 parameters, the description should compensate but largely does not: limit, ticker, date_from, and date_to get no added meaning. It does loosely gesture at filterable dimensions via the named result fields (company, form, filing date), but no syntax or semantics are added beyond the schema.

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 and resource — 'Full-text search over SEC filings (EDGAR FTS)' — and pins the upstream source (efts.sec.gov) plus the normalized result shape. This cleanly separates it from the event-, insider-, and 13F-oriented EDGAR siblings.

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 description never says when to prefer this tool over alternatives such as gov_edgar-events or gov_edgar-watch, nor does it state prerequisites or exclusions. Only implied usage ('full-text search') is available, so the agent must infer the selection case on its own.

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