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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral context by disclosing the $0.004 USDC per-call cost via x402. It stops short of explaining the payment flow itself (wallet/auth prerequisites) despite an `x402_check` sibling existing.

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?

Two sentences, front-loaded with purpose and event scope, with the cost detail placed last where it belongs. The long category enumeration is informative rather than padding, though it could be trimmed slightly.

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 does some of the work by describing red-flag highlighting and filing links, which hints at return shape. However, it leaves `limit` semantics and the x402 payment prerequisite unexplained, which are real gaps for a paid three-parameter tool.

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 `days` is documented ('Look back, default 365'), while `limit` and `ticker` have no descriptions. The prose adds nothing about any parameter, so it fails to 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 names a specific resource (material events at US public companies from SEC 8-K filings) and enumerates concrete event categories, so the scope is unmistakable. It never names or contrasts a sibling such as `filings` or the generic `events`, leaving the agent to infer the distinction between raw filings and decoded events.

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?

There is no 'use this when' guidance, no exclusions, and no alternative tool (e.g. `filings`, `insider`, `company`) is named as the right choice under different conditions. The only routing signal is the implied SEC-8-K domain, which the agent must derive on its own.

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