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

With no annotations, the description carries the full burden and does well: it discloses official SEC data, no API key, a pay-per-call price, and the 402 challenge behavior on unpaid calls. It stops short of describing result limits, pagination, or query syntax, which leaves some behavioral gaps.

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 three front-loaded sentences with no wasted filler; purpose and return shape come first, then data source, then payment terms. The payment sentence is dense but earns its place because it prevents a failed unpaid call.

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 three-parameter search tool with no annotations and no output schema, the description covers purpose, return fields, auth, and pricing. It is incomplete on parameter semantics and result behavior, which an agent would still need before invoking confidently.

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 nominally 100%, but the schema text for q, to, and from is only 'required' or 'optional' with no real semantics. The description adds nothing about the query string or date-range meaning of these parameters, so 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 names a specific verb (full-text search) and resource (every SEC EDGAR filing), lists covered form types, and clearly distinguishes this from company-specific retrieval such as edgar_company. An agent can tell exactly what this tool does without opening the schema.

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?

Usage is implied by the contrast between full-text search and the sibling edgar_company, but the description never explicitly says when to use this versus edgar_company or caselaw_search. There are no exclusions or routing conditions beyond the implicit 'search broadly' framing.

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