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

Adds real value beyond the lone destructiveHint annotation: it discloses the auth requirement, that only a fixed set of fields are mutable, that status changes are a distinct operation, that a dry-run mode exists, and why cancel is excluded (a late cancel can charge the client). It stops short of describing the response or whether email sends are side effects by default.

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?

Front-loaded with the core action, then constraints, dry-run, auth, and endpoint. Every sentence carries information; no 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 9-parameter mutation tool with no output schema and minimal annotations, the description covers mutability scope, status actions, dry-run, and auth. It lacks only details on return payload/confirmation and default email behavior, which are minor gaps.

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 baseline is 3, but the description goes further by asserting the listed fields are the exhaustive set Mindbody permits changing and by framing test: true as a validation-only dry run. That meaning is complementary to, not a restatement of, 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?

States a specific verb+resource (reschedule/edit an appointment) and enumerates exactly what can change (start/end time, staff, session type, notes) plus the status transitions. This cleanly distinguishes it from sibling mindbody_add_appointment, which creates rather than edits.

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?

Gives clear context for use, states prerequisites (staff user token), a dry-run path (test: true), and explicitly rules out cancel/late-cancel with a reason. It does not, however, name the sibling tool an agent should use instead for cancellation, so the routing guidance is incomplete.

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