evite_cancel_event

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

The description discloses critical behaviors beyond annotations: 'DESTRUCTIVE,' potential guest notification, dry-run behavior, and reversibility. This significantly enriches the agent's understanding of side effects. The readOnlyHint=false annotation is consistent with the destructive warning; no contradiction.

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?

Three compact sentences front-loaded with the action, followed by the essential safety caveats. Every sentence contributes necessary information with no redundancy or fluff.

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 description covers the destructive nature, confirm-gated workflow, and reversibility, which are the key contextual concerns for a cancel operation. No output schema exists, so return details are not described, but the dry-run preview is mentioned. A slightly more detailed preview description could push this to 5, but it is sufficiently complete for 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 coverage is 100% for both parameters, and the description adds further meaning by explaining the confirm parameter's role in dry-run vs. actual cancellation. The event_id parameter is already described in the schema with its source (evite_list_events), so the description adds value beyond the schema.

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, 'Cancel an Evite event,' and clarifies 'also used to delete a draft.' This distinguishes the tool from siblings like evite_list_events, evite_get_event, and evite_create_event, and explicitly names evite_reinstate_event as the reversal tool, making the purpose 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?

Clear usage guidance is provided: the tool is confirm-gated ('without confirm:true this returns a dry-run preview and cancels nothing') and reversible via evite_reinstate_event. It doesn't explicitly list exclusions or when-not-to-use, but the context is sufficient for an agent to decide when to invoke it.

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