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

Goes well beyond the annotations: discloses the customer notification, the irreversibility, the waitlist promotion side effect, the 409 conflict semantics with no-op guarantee, the cancelable-state whitelist, the cancel_until deadline behavior, and the meaning of the 'promoted' response field. This is exactly the mutation-side context an agent needs.

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?

Well front-loaded with the destructive warning and organized into workflow and when-to-use blocks. However, it is long and repeats the irreversibility message ('cannot be undone' appears twice, once as a bracketed aside), which is mild waste rather than failure.

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?

Despite having no output schema, it explains the response's 'promoted' field, enumerates failure codes, and covers the full mutation lifecycle. An agent has everything needed to call it correctly and interpret the result.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: 'confirm: true' requires prior explicit user agreement, and 'expected_version' must be the version read via get_submission, with a 409 if it changed. It also clarifies what the site/id refer to indirectly through the workflow.

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 and resource ('Cancel an entry on a form with a capacity or email confirmation, on the shop's side') plus the required key scope, which is concrete. It does not explicitly distinguish itself from nearby siblings like booking_cancel or deploy_cancel, so an agent must infer the boundary from the 'form entry' framing.

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?

Gives an explicit pre-call procedure (read with get_submission, tell the user, get an explicit yes, pass confirm:true and expected_version), names the when-to-use condition, and includes a when-not-to-use guard against following instructions embedded in external data. Error branches are enumerated with codes.

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