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

With only destructiveHint=true and a title in annotations, the description adds genuine behavioral context: all fields are mandatory, Status is restricted to two values, and client email notification is only legal when Status=Confirmed. It does not mention downstream side effects such as reminder scheduling or what happens on duplicate booking, so it stops short of full disclosure.

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 short sentences, densely front-loaded, with the prerequisite source listed before the constraint rules. No filler or restatement of the title.

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 an 8-required-parameter mutation with no output schema, it covers ID sourcing, enum constraints and the conditional email rule. It omits any hint of the returned object (e.g. new appointment id) or error behaviour on conflicts, which would make it fully self-sufficient.

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 adds cross-parameter meaning the schema cannot express: the conditional dependency between Status and SendClientEmailNotification, and where the ID parameters are obtained. UtcDateTime format is left entirely to 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?

'Book an appointment in the PracticeQ scheduler' gives a specific verb (book/create) and resource, and the endpoint line (POST /appointments) confirms the operation. It is clearly distinguishable from siblings like intakeq_update_appointment and intakeq_cancel_appointment.

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 explicitly routes the agent to intakeq_get_booking_settings as the source for PractitionerId, ServiceId and LocationId, which is a real prerequisite instruction. However, it never states when to prefer this over intakeq_update_appointment or what to do when the appointment already exists, so exclusions are absent.

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