nws_public_witnessing_cancel_assignment

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

With no annotations, the description usefully discloses that cancellation does not write remote data. However, it omits other important traits such as whether the operation is idempotent, what happens to the preview afterward, and whether authentication or ownership is required.

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 compact sentence with the key action and safety property front-loaded. There is no wasted wording.

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 cancellation tool with a required confirmation_id and no annotations, the description is too thin. It does not explain the parameter's source or the post-cancel state, although the presence of an output schema reduces the need to describe return values.

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%, and the description never mentions confirmation_id or explains where to obtain it. The sentence implies a confirmation identifier exists, but it adds essentially no semantic guidance for the sole required parameter.

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?

It states a specific verb and resource: cancel a pending shift-assignment preview. This distinguishes it reasonably from preview_assignment and commit_assignment, though it does not explicitly name sibling alternatives or the exact preview lifecycle stage.

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 'pending shift-assignment preview' implies this should be used on an already-created preview, but it never states when to choose cancel versus commit or what prerequisites must exist. Usage is inferable but not explicit.

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