confirm_event

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

The description adds behavioral context beyond annotations, such as the requirement for 'hold' status and the firing of lifecycle webhooks. Annotations already indicate idempotent and non-destructive, and description aligns without contradictions.

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 concise with two sentences, no extraneous words, and front-loads the primary action. Every sentence adds necessary value.

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 preconditions, the mutation effect, and webhook behavior. It is adequate for a simple tool with one parameter and no output schema. Missing error or success details, but acceptable.

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?

The single parameter 'event_id' is fully described in the schema (100% coverage). The description does not add further semantics for the parameter itself, but the overall tool description provides context for its usage.

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 clearly states the action ('promote a held event to a confirmed booking') and the resource. It distinguishes from siblings like cancel_event or release_event by specifying the 'hold' status requirement.

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 provides explicit conditions for use: event must have status='hold' and hold_expires_at not passed. It does not explicitly state when not to use or mention alternative tools, but the conditions are clear enough for proper selection.

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