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

With no annotations, the description carries the full burden. It usefully discloses the return content (structured JSON with extractive summaries and filing links) and operational facts (HTTP GET, $0.02 via x402 pricing, docs link), which is real value beyond a bare name. However it omits recency/pagination semantics implied by 'Latest', auth/permission requirements, and how the coverage window is bounded.

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?

Three sentences, purpose front-loaded, and the bracketed HTTP/pricing/docs footer is compact. There is mild redundancy ('structured JSON' appears twice) but no 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?

No output schema exists, and the description partially compensates by pointing to the shared /v1/edgar/events shape and listing what each record carries. It falls short for a 3-parameter, annotation-free tool: the required limit and the ticker filter are never explained, leaving an agent to guess at core invocation behavior.

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 33% (just the 'since' filter), and the description mentions no parameters at all. The required 'limit' (with min 1 / max 50) and the 'ticker' filter are documented nowhere in either schema or description, so the description does not compensate for the coverage gap.

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 and resource ('Latest material definitive agreement 8-K events as structured JSON') and pins the exact classification (Item 1.01). It explicitly differentiates itself from siblings by noting it is 'Same shape as /v1/edgar/events, pre-filtered to Item 1.01 events,' so an agent can separate it from the other gov_edgar-events_* category tools.

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 description makes the selection condition clear: use this when you want Item 1.01 material-agreement events specifically, versus the unfiltered gov_edgar-events or the other category variants. It stops short of explicitly naming a sibling alternative or stating when-not to use it, so it lands just below the top.

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