pws_cancel_network_deal

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

Annotations already mark the tool as destructive and not read-only; the description adds that it can preview or cancel, which is useful. But it leaves critical behavioral details unexplained: whether preview is side-ffect-free, whether confirmed=true is mandatory for actual cancellation, whether cancellation is immediate or reversible, and what happens if the deal is already canceled. For a destructive action, this is a significant transparency gap.

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 two short sentences with no filler. The primary purpose is front-loaded in capital letters, and the second sentence provides a boundary in one line. Every word earns its place.

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?

For a destructive, non-idempotent tool with three undocumented parameters and no output schema, the description should explain the preview/confirmed flow and cancellation consequences. It does neither fully. An agent cannot determine how to execute a cancel safely or whether the preview step is mandatory, so the definition is incomplete for real invocation.

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%, so the description carries the full burden for explaining dealId, preview, and confirmed. It offers only the word 'PREVIEW,' vaguely suggesting the preview param's role, but it never defines confirmed, the relationship between preview and confirmed, or why confirmed exists. This is insufficient for an agent to call the tool confidently.

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 opens with a specific action pair, 'PREVIEW OR CANCEL,' and identifies the exact resource (a player-company network deal). It is distinct from sibling tools like pws_get_network_options, which lists options rather than previewing or canceling them. The additional sentence clarifies that renegotiation happens elsewhere, further scoping the tool.

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 this tool is for previewing or canceling deals and states that new terms are handled inside PWS, which signals not to use this tool for negotiation. However, it does not explicitly say when to prefer this over pws_get_network_options or any other alternative, nor does it describe the preview-then-confirm workflow. Usage context is therefore more implied than fully specified.

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