kalshi_cancel_order

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It only adds 'respects dry-run,' which is a notable behavioral trait but is not explained—what does respecting dry-run mean for the actual cancellation? It does not mention side effects, error behavior, or whether the operation is reversible. This is minimal and leaves significant ambiguity.

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?

The description is a single, concise sentence with no wasted words. The action and key qualifier are front-loaded, making it immediately scannable. It is an exemplary model of brevity for a simple 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?

The tool is simple with one parameter and has an output schema, which covers return-value details. However, the description omits explanation of the dry-run behavior, potential failure modes, or any conditions that might affect execution. Given the complexity is low, a slightly more descriptive note on what 'respects dry-run' entails would improve completeness. As it stands, it is adequate but not thorough.

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?

The parameter 'order_id' has no description in the schema, and schema description coverage is 0%. The description's phrase 'by id' clarifies that the parameter is the identifier of the order to cancel, which adds minimal semantic value beyond the schema. However, it does not specify any format, constraints, or validation rules. For a single, obvious parameter, this is acceptable but not rich.

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 verb 'Cancel', the resource 'Kalshi order', and the method 'by id'. It fully conveys what the tool does and is specific enough to stand alone, distinguishing it from other operations like placing orders or fetching data.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or conditions under which this tool should be chosen over the sibling 'cancel_order'. The parenthetical about dry-run hints at a condition but does not explain it or tie it to usage decisions.

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