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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses real behavioral traits: synonym expansion ('contact center also finds call center'), query operators (quotes, OR, leading minus), the coverage window ('last 12 months'), and the audience restriction ('public companies only'). These are non-obvious semantics an agent could not derive from the schema or annotations.

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?

Purpose is front-loaded in the first clause, and the return-value sentence follows logically. The example-question list is longer than strictly necessary and could be trimmed, but each sentence carries usable information rather than filler.

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?

With no output schema, the description compensates by enumerating the returned fields (matching passage, company, form, filing date, section, EDGAR link) and by stating coverage limits and matching rules. An agent has everything needed to call it and interpret the response.

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 baseline is 3, and the description earns an extra point by explaining query syntax (quoting, OR, minus) and the synonym behavior that governs how the required 'query' parameter is interpreted, plus confirming the watchlist scoping. It does not clarify the days/limit/page interaction beyond what the schema already documents.

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 inside SEC filings' — and enumerates the covered document types (10-K, 10-Q, 20-F, 8-K) and their sections, which tells an agent exactly what corpus it searches. It does not, however, explicitly differentiate itself from the sibling search_sec_filings, leaving the agent to infer that this one searches document text while that one presumably searches filing metadata.

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?

Offers concrete use-case questions ('which banks mention contact centers in their 10-K', 'did Verizon talk about headcount') and notes the watchlist-scoped variant, giving a clear sense of when this tool fits. It stops short of naming an alternative tool or stating when NOT to use it, so routing versus search_sec_filings remains implicit.

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