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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior: results are newest-first and include future-dated events such as a pending regulator review end date. It does not mention the default limit of 25 or any pagination/truncation behavior, which matters for a list tool.

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 compact sentences with the resource and ordering front-loaded. The trailing filter sentence is slightly redundant with the schema but still earns its place as a quick usage cue.

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?

No output schema exists, yet the description conveys ordering, inclusion of future events, and the filterable dimensions, which is most of what an agent needs. The main gap is the default result limit and any truncation behavior for a list-returning 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 coverage is 100%, so all six parameters are already documented in the schema, making 3 the baseline. The description reinforces the date-range, event-type and contract filters and hints at upcoming_only via 'dates still to come', but adds no syntax or semantics beyond the schema.

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 (announcements, exchange filings, regulator actions on compute derivatives) with a clear verb-like listing action and ordering (newest first). The resource is distinct from siblings like compute_list_prices and search_compute_contracts, though it never names them explicitly.

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?

'Filter by date range, event type or contract' implies how to narrow results, but there is no explicit when-to-use guidance, no exclusions, and no pointer to an alternative sibling tool for related queries.

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