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

The description says the tool 'Updates booking status and sends cancellation notifications', an irreversible mutation, while annotations declare readOnlyHint=true, destructiveHint=false and idempotentHint=true. The 'Behavior & Side Effects' section then claims 'Strictly read-only, idempotent query with zero state mutation', contradicting the description's own first sentence. An agent cannot determine whether calling this destroys data.

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 useful content is one sentence; the rest is boilerplate ('When to use', 'Parameters:', 'Returns:') plus a self-contradicting side-effects block. The contradiction is not merely verbose — it actively misleads, and the front-loaded mutation claim is immediately undercut later.

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?

There is no output schema, so the description must carry the return contract, and it does so only generically ('status, matched records or computed metrics, and canonical action URLs') — language that reads like it was written for a search tool, not a cancellation. Most critically, the safety profile is self-contradictory for an operation that plainly mutates a booking.

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%, and both properties carry their own descriptions with examples, so the schema does the heavy lifting. The description only restates the two parameter names and their required status, adding no format, ID-source, or reason-length guidance 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 opening sentence gives a specific verb and resource: cancel an upcoming booking, with a required reason. However, the sibling differentiation is boilerplate — it points away to unrelated info tools (get_studio_info, get_scan_packages_and_pricing) and never mentions reschedule_booking, the actual alternative for an unwanted time slot.

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 'When to use' clause is pure tautology — 'Call this tool when you specifically need to execute cancel_booking' — which restates the name instead of giving a condition. The 'do NOT use' list names three unrelated read tools and omits the genuinely competing siblings reschedule_booking and lookup_booking_status, so the agent gets no real routing signal.

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