Material events

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

Annotations indicate readOnlyHint and openWorldHint, so the tool is a safe, read-only operation with potentially dynamic results. The description adds behavioral details: auto-pagination via max_items, cursor-based pagination, and ordering. It does not contradict annotations and provides useful context beyond them.

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, each packed with information: purpose and filtering in first sentence, pagination and alternative tool in second. No wasted words, well front-loaded.

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?

Despite no output schema, the description covers purpose, filtering, pagination modes, ordering, and alternative tool. It is sufficient for an agent to select and use the tool correctly. Minor omission: no mention of response structure, but not critical.

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?

All parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds value by explaining how cursor, limit, and max_items work together for pagination, and notes optional filtering. This synopsis elevates the score above baseline.

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 tool lists a company's 8-K material-event filings, with optional filtering by item code. It distinguishes itself from the sibling tool stocks_earnings by specifying the alternative use case.

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?

Explicitly guides when to use this tool (for 8-K filings) and when to use stocks_earnings (for earnings releases). Also explains pagination strategies with cursor/limit or max_items, and ordering (most recent first).

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