Reschedule an appointment

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

Annotations indicate the tool is not read-only (readOnlyHint false), not idempotent, and not destructive. The description adds that duration is unchanged and that availability is validated by default, giving meaningful behavioral context beyond 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 description is two sentences with no irrelevant information. First sentence states the core action, second adds an important behavioral detail. Every word earns its place.

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?

Given the tool's moderate complexity (3 parameters, no output schema), the description covers purpose, key behavior, and parameter semantics. It does not mention return values or errors, but the core functionality is sufficiently described.

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?

The description adds value by explaining that start sets the new time and ignoreAvailability bypasses validation. Schema already describes two of three parameters; the description clarifies their effect. The appointmentId parameter is assumed but not elaborated.

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 'Move an appointment to a new start time' using a specific verb and resource. It distinguishes from siblings like book_appointment (create) and cancel_appointment (delete) by focusing on rescheduling with unchanged duration.

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 explains that availability is validated unless ignoreAvailability is set, providing context on when to use that parameter. However, it does not explicitly state when not to use this tool versus alternatives, though the purpose is clear.

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