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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds substantial non-obvious context: changes affect live booking choices and prices, passes are stopped from sale rather than deleted, removals must be confirmed first, and on multi-design sites it performs a build that returns a new site_id and a build_transition whose tell_user must be relayed. This is rich behavioral disclosure beyond the annotations.

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 WHAT/WHERE/WHOM framing front-loads the core purpose efficiently and each subsequent paragraph covers a distinct concern (ordering, payment rules, prerequisites, publish timing, build_transition). It is dense and long, but nearly every sentence carries actionable information rather than filler.

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 complex 7-parameter mutation tool with no output schema, the description covers orchestration order, prerequisites, destructive-change confirmation, live-effect timing, and the multi-design build/variation_id flow. An agent has enough to call it correctly without opening the schema.

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?

With 100% schema coverage the baseline is 3, but the description adds real semantics: name-based matching ('"Sam" updates Sam'), the payment/confirmation dependency rule, the branch→people→services ordering constraint, and variation_id omission behavior. These go beyond what the schema states, though much of the per-field detail duplicates the schema's own descriptions.

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 uses a clear metaphor ('Set up WHAT people book, WHERE and WITH WHOM, and the packs and memberships they can buy') that maps directly to the services, locations, staff and passes parameters. It is specific about the resource and scope, but it does not explicitly name the sibling tools it differs from (e.g. set_up_appointments, manage_appointments, spin_up_pack), leaving that differentiation to inference.

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?

It gives a concrete triggering condition ('use it whenever the owner describes more than one thing to book...') and a prerequisite ('read get_appointments_status' before calling) plus an explicit call order (branches, then people, then services). It also says to confirm replacements/removals before calling. It stops short of naming when to prefer the adjacent appointment tools instead.

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