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

With no annotations, the description carries the full behavioral burden and discloses meaningful traits: it is an HTTP GET read endpoint, costs $0.02 via x402, exposes documentation, returns structured JSON with extractive summaries and filing links, and matches the /v1/edgar/events shape. It omits pagination behavior, rate limits, and authentication specifics beyond the x402 payment note, keeping it below 5.

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 first sentence front-loads the resource and purpose, the second adds classification detail, and the third routes the agent to the generic sibling. The HTTP/pricing/docs bracket is compact reference metadata rather than prose bloat, so 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?

With no output schema, the description usefully conveys return content (structured JSON, summaries, links) and the Item 4.02 filter, which helps an agent understand results. However, it leaves key invocation details unexplained, notably the behavior of the required 'limit' and optional 'ticker' parameters and pagination semantics, making it only minimally complete.

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 only 33% (only 'since' is documented in the schema), and the description adds no meaning for 'limit,' 'ticker,' or even 'since.' It fails to compensate for the low coverage, so an agent must reverse-engineer the required limit and optional ticker filters entirely from bare schema constraints.

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?

States a specific resource and scope: 'Latest restatement and non-reliance 8-K events' filtered to 'Item 4.02,' which distinguishes it from the broad gov_edgar-events sibling and from other event-specific siblings like bankruptcy or acquisitions. An agent can identify the exact data slice without opening the schema.

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?

Provides clear routing context by naming the generic endpoint it mirrors ('Same shape as /v1/edgar/events, pre-filtered to Item 4.02 events'), implying when to choose this tool over the unfiltered one. It stops short of an explicit when-not or a direct 'use X instead' instruction, so it does not reach 5.

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