Delete Appointment Group

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

The description discloses the destructive nature (delete group) and additional side effects: cancelling reservations and notifying participants via cancel_reason. This goes beyond the annotation destructiveHint:true by specifying what is affected and the notification behavior, making it fully transparent.

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, consisting of two short sentences. It is front-loaded with the primary action and provides necessary detail without any fluff or redundancy. The structure is clear and easy to parse.

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 operation with two parameters, the description is complete enough. It explains the main action and the effect of the optional parameter. It does not mention error handling or return values, but with no output schema and a straightforward destructive action, the description covers the essential context needed for an agent.

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 description explains the purpose of cancel_reason (to notify participants), adding meaning beyond the schema's generic 'Message to include in cancellation notifications.' The appointment_group_id is self-explanatory and not further elaborated, but the description does provide useful context for the optional parameter, improving parameter understanding.

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: delete an appointment group and cancel existing reservations. It uses specific verbs (delete, cancel) and specifies the resource (appointment group), distinguishing it from other appointment group tools like get, create, update, and list.

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. The usage is implied: you use it to delete an appointment group. It does not mention conditions or exclusions, but the action itself is straightforward. The optional cancel_reason for notifications is noted, but no guidance on when to provide it is given.

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