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

No annotations are provided, so the description carries the full behavioral burden. It is a destructive mutation but never states whether cancellation is irreversible, what permissions or auth are required, what happens to partially filled orders, or what the failure modes are. Only the basic action is conveyed.

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?

A single tight sentence with the action and key identifier front-loaded. Efficient, though it is arguably too terse for a destructive operation.

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?

An output schema exists so return values need not be explained, but for a destructive cancel with zero annotations and 0% parameter coverage, the description omits critical context: irreversibility, auth requirements, and what the optional ticker and platform parameters do.

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 0% for three parameters. The description maps 'venue order ID' to order_id and names the two platforms, giving partial meaning, but the required-vs-optional distinction (order_id required, platform defaults to kalshi) and the optional ticker parameter are entirely unaddressed.

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 (cancel), resource (active open order), and scope (Kalshi or Polymarket via venue order ID). Easily distinguished from siblings like foresea_place_order and foresea_preview_order.

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?

The phrase 'active open order' implicitly constrains when the tool applies, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g., an order must exist and not already be filled), and no routing to alternatives.

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