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

Beyond the readOnly/openWorld/idempotent annotations, it discloses the full return payload (company, CIK, tickers, filing date, accession, decoded items, doc/index URLs, retrievedAt), error semantics (400 invalid input, 503 SEC rate limit busy), and the paid x402 flow including the retry parameter. This is behavior an agent cannot get from the structured fields.

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?

Front-loaded with purpose, then scope, then return/error/payment details, with zero filler sentences. The single run-on first sentence packs many clauses together, which slightly hurts scannability, but nothing is redundant.

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 seven-parameter, no-output-schema tool, the description covers return fields, error states, rate limits, and the payment handshake, which is most of what an agent needs. Gaps remain around default behavior when no parameters are supplied and the meaning of since/until/limit.

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 only 29%, so the description has to compensate. It usefully explains that ticker or CIK selects one company, that items takes codes with human-readable meanings, and that q is a full-text phrase; however since, until, and limit are never mentioned, leaving three of seven parameters with no narrative meaning.

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 opening clause states a specific verb+resource: 'SEC 8-K current reports from EDGAR', then scopes the two modes (one company by ticker/CIK vs. market-wide latest). It does not name the sibling sec_filings, so an agent cannot fully distinguish this from the broader filings tool from the definition alone.

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?

'Useful for event monitoring and research' plus concrete item-code examples (2.02 earnings, 5.02 officer changes, 1.01 agreements) give an agent a clear sense of when this fits. No explicit when-not guidance or named alternative is offered, so routing against sec_filings still requires inference.

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