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

The readOnlyHint and destructiveHint annotations already establish this is a safe, non-destructive read operation. The description adds valuable behavioral context beyond those annotations: it names the external source (SEC EDGAR), states the response format (JSON), and discloses the financial cost ($0.01 USDC via x402), which is especially important for a paid tool.

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 somewhat repetitive: 'SEC filings full-text search (EDGAR)' and 'Full-text search across SEC filings' state the same idea, and 'Source: SEC EDGAR full-text search' repeats it again. While all included facts (purpose, output, source, format, price) are relevant, the redundancy makes it less lean than it could be.

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 simple read-only tool with three parameters and no output schema, the description covers the essentials: what it searches, what it returns (metadata and links), the output format, the external source, and the price. It does not detail sorting or pagination, but the limit parameter partially addresses result control and the schema provides the necessary input semantics.

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 schema already fully documents q, form, and limit. The description only paraphrases the form filter ('filter by form type') and adds no new semantic details about parameter formatting, defaults, or edge cases, leaving it at the baseline.

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 states a specific verb ('Full-text search') and resource ('SEC filings'), explicitly notes filtering by form type, and mentions the return value ('filing metadata and links'). This clearly distinguishes it from sibling tools like sec_company and sec_company_snapshot, which focus on company data rather than full-text filing search.

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 intended use is implied: search across SEC filing documents, optionally filtered by form type. However, the description does not contrast this with siblings such as sec_company or sec_company_snapshot, nor does it state when NOT to use this tool, so an agent gets no explicit routing guidance.

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