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

Unlike what annotations supply, the description discloses the pricing model ($0.02/call via x402), the free 404 FILING_NOT_FOUND path, the fact that invalid input and upstream failures are not settled, a 10-event cap, and that text is returned as clean prose with EX-99 exhibits. It also supplies the 4-business-day reporting context. Minor gap: no explicit rate limits or idempotency caveats beyond what annotations imply.

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?

It front-loads the agent's core question and then packs pricing, exhibits, filtering, and error semantics efficiently. It is long for one paragraph, but nearly every clause carries operational information; only minor streamlining is possible.

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 7-param, 0-required read-only tool with no output schema, the description covers what is returned (item codes with official titles, clean-prose 8-K text, EX-99 events), how it is filtered, how to identify a specific filing, cost and error handling. Nothing critical for correct invocation is missing.

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 100%, so the schema already documents every field, establishing a baseline of 3. The description adds value by explaining the item-code mechanism with concrete examples (5.02 executive changes, 2.02 earnings, 1.05 cyber), describing the accession-number route and its source, and confirming ticker/CIK lookup, which improves on the schema's short field descriptions.

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 opens with a plain-language question, states the specific resource (US public company 8-K filings from SEC EDGAR), and enumerates the concrete event types it returns. It clearly distinguishes itself from siblings like sec_list_filings (which it names as the free lister) and sec_filing_section.

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?

It gives explicit use cases (event monitoring, news/earnings agents, due diligence, trading research) and routes agents to sec_list_filings for accession numbers, and to ticker/CIK for lookup. It lacks explicit 'when not to use' guidance versus sec_filing_section, but the context is clear enough to select correctly.

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