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

Annotations only carry destructiveHint=true, so the description adds real value: no payment is taken by default, require_payment forces a usable pricing option, and test:true validates without committing. It also discloses reversibility ('Undo from the Mindbody front desk'), which is important for a write operation.

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?

Five tight fragments, front-loaded with the action and variant, then payment behavior, undo path, dry-run, and endpoint. Every sentence adds distinct operational value with no redundancy.

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?

With no output schema and only a destructiveHint annotation, the description still covers payment, dry-run, waitlist, and reversibility well. Minor missing pieces like confirmation-email behavior (covered only in the schema) keep it just under complete.

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 the schema already documents all seven parameters, making 3 the baseline. The description reinforces the semantics of require_payment and test and clarifies the default (no pricing option needed), but adds little beyond the schema's own parameter 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 description states a concrete verb and resource — booking a client into a class — and clarifies the waiting-list variant in the same sentence. It clearly differs from mindbody_add_appointment by the 'class' resource, though it does not explicitly name that sibling.

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 implied context (booking vs waitlist, dry-run via test:true, undo via front desk) but never states when to prefer this tool over the appointment or list siblings. The guidance is present but left for the agent to infer.

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