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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description goes further than the annotations by disclosing the temporal coverage (since 2001), the returned fields, and a per-call price of $0.004 USDC via x402 — a real cost constraint an agent needs before calling. Pagination/limits behavior is still undisclosed.

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?

Two sentences, front-loaded with the core capability before the parenthetical form list and the cost note. Dense but every clause carries information; the form enumeration is long but legitimately scopes coverage.

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 correctly spends words on return content ('which companies mention a phrase, in which filing and when, with direct document links') and adds cost and coverage window. The main remaining gap is result-count/pagination behavior for a limit-bearing search tool.

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 coverage is 0%, so the burden falls on the description, and it only partially compensates: 'form' maps to forms, 'date range' to from/to, and 'company' plausibly to ticker. The required q parameter and limit are never explained, and there is no format guidance (date syntax, form codes, result count) for any of the six parameters.

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 across every SEC filing'), enumerates the covered form types, and describes what comes back (company, filing, date, document links). It never names its closest siblings (sec_financials, sec_events, filings), so the agent still has to infer which SEC tool to pick, but the 'full-text' framing is itself reasonably distinguishing.

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 rather than stated: 'filter by form, date range and company' tells the agent what it can narrow on, which suggests query-style lookups. There is no explicit when-to-use clause and no pointer to sec_financials or sec_events for structured statement data, so routing against siblings remains a guess.

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