pws_cancel_show

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

Annotations already flag destructiveHint=true, but the description adds useful behavioral context: the dual preview/cancel modes, the default preview behavior, and the verification of a cancellation flag. This goes beyond the structured hints without contradicting 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?

The description is a single, front-loaded sentence that efficiently communicates the core purpose and key defaults. The phrase 'Verifies the cancellation flag' is a bit cryptic but still earns its place by hinting at the confirmation mechanism.

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 complex (dual preview/cancel), has 3 parameters, and no output schema. The description does not explain what the call returns, what cancellation actually does (beyond destructive), or the exact role of the 'confirmed' flag. For a potentially destructive action, this is insufficient context.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It explains 'Defaults to preview' (relating to preview) and 'Verifies the cancellation flag' (likely confirmed), but it doesn't fully clarify how confirmed works or what showId represents. Some meaning is added, but gaps remain.

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 specifies the exact actions 'PREVIEW OR CANCEL' and targets 'an unfinished player-company show', making it distinct from sibling tools like pws_get_show or pws_plan_show. The verb+resource pairing is clear and unambiguous.

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 description implies usage for unfinished shows and indicates a preview default, but it doesn't explicitly contrast with alternatives like pws_get_show or pws_apply_show_plan. No when-not-to-use or alternative tool guidance is provided, leaving the decision partially implicit.

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