Delete Appointment Group

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

Annotations already declare destructiveHint=true, and the description complements this by revealing that deletion also cancels existing reservations and that cancel_reason triggers participant notifications. This adds meaningful behavioral detail beyond the annotation, without 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?

Two short sentences with no fluff. The primary action is front-loaded, and the optional parameter guidance is placed after the main statement. 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 simple delete tool with a clear destructive annotation and a 100% schema-documented required parameter, the description covers the key behavior and one optional usage detail. It does not mention the required appointment_group_id explicitly, but the schema covers it. No output schema exists, so no expectation to describe return values. Overall, it's sufficient.

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 both parameters are already documented. The description adds little beyond the schema: it mentions cancel_reason is used to notify participants, but the schema already says 'Message to include in cancellation notifications.' No additional syntax or meaning is provided, keeping this at the baseline.

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 states a specific verb ('Delete') and the resource ('appointment group'), and adds a concrete side effect ('cancel any existing reservations'). It clearly distinguishes this tool from its siblings (get, create, update, list) which do not delete.

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 does not explicitly state when to use this tool versus alternatives like update_appointment_group. It only mentions the optional cancel_reason for notifications, but gives no guidance on when deletion is appropriate or when not to use it. The name implies deletion, but the absence of explicit usage context leaves some room for inference.

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