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

The destructive nature is already indicated by destructiveHint=true, and the description adds meaningful side-effect context: the client is notified and owner confirmation is required before acting. It does not contradict the annotations and gives useful behavioral guidance beyond the structured hints.

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 three short, purposeful sentences with no filler. It front-loads the key scope and action, then adds the confirmation requirement and side effect efficiently.

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 who can use the tool, what it does, what side effect it has, and a mandatory workflow step. It does not describe return values or failure cases, but no output schema exists and the more important safety aspects are covered by annotations.

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 description coverage is 0%, and the description does not explain booking_id or reason. The parameter names are somewhat self-explanatory, but the description provides no additional semantic meaning, constraints, or guidance beyond the raw property names.

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: "Cancels a booking on behalf of the business and notifies the client." It also specifies the actor and scope with "Only for business owners signed in to Awning," which distinguishes it from the sibling cancel_booking. The operation is specific and 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?

The description explicitly restricts usage to business owners and instructs the agent to always ask the owner to confirm first. It implies the tool is the owner-side variant of cancellation, though it does not explicitly contrast it with cancel_booking or mention edge cases like already-cancelled bookings.

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