SEC 8-K material events (real-time)

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

Beyond annotations (readOnlyHint=true, openWorldHint=true), the description adds concrete behavioral details: it is a real-time stream, sorted descending by filing time, capped at 40 per call, and has a per-call cost of $0.005 USDC settled via x402. This discloses rate limits, pricing, and stream semantics, exceeding what annotations alone provide.

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 two sentences, front-loads the core purpose, and packs essential operational details (sorting, limit, pricing) without any fluff. Every sentence earns its place.

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 tool with no parameters, no output schema, and simple annotations, the description covers the main aspects: what data is returned, the ordering, the limit, and the cost. It does not specify the exact response structure, but that is not required given the absence of an output schema and the event-type examples already given.

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?

The input schema has zero parameters, so the description need not add parameter-level detail. According to the baseline rule for zero parameters, a score of 4 is appropriate; there is nothing to compensate for.

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 clearly states the verb 'stream' and the resource 'SEC EDGAR 8-K current reports', enumerates representative event types (M&A, officer changes, earnings releases, etc.), and distinguishes itself from siblings by focusing on real-time 8-K coverage specifically.

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 provides clear context: it is a real-time stream of 8-K events sorted by filing time, which implicitly tells when to use it (when real-time 8-K data is needed). However, it does not explicitly mention alternatives or exclusions relative to sibling tools like sec_filings_today, so it doesn't reach the 'explicit when/when-not' level.

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