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

Annotations already declare the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds genuinely new context: the data source (SEC EDGAR current filings) and the cost model (0.01 USDC per call via x402 across listed chains), which an agent must know before invoking. It does not state rate limits or latency.

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, front-loaded with the usage condition, followed by returns and source/cost. The field enumeration is slightly long but earns its place by naming the item-code taxonomy; no filler sentences.

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 one-parameter read tool with an output schema and full annotation coverage, the description covers purpose, source, cost, and example item codes, so an agent can call it correctly. The one meaningful gap is failing to distinguish it from the sibling get_sec_filings.

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 100%, so the single 'hours' parameter (1-72, default 24) is fully documented in the schema. The description only echoes the window concept without adding format or constraint detail, so baseline 3 applies.

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 verb and resource ('Returns the 8-K filings filed across the market in the window') and enumerates the returned fields and item codes. However it never differentiates itself from the sibling get_sec_filings, so an agent cannot tell the two apart from the description alone.

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?

'Use when an agent needs the material events US companies disclosed in the last hours' gives a clear triggering context, and the time-window framing narrows the use case. It offers no when-not guidance and does not name an alternative (e.g. get_sec_filings) for other filing needs.

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