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

Annotations only supply destructiveHint=true; the description carries the rest: irreversible through this server, the reason's billable rate may create a cancellation charge, and the patient may be notified per practice settings. It also discloses the two underlying endpoints, so an agent knows the exact write path.

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 WRITE marker, then consequences, then the group-appointment branch, then the safety gate. Every sentence conveys distinct operational information; nothing repeats the schema verbatim.

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?

No output schema exists, yet the description covers effect (cancellation), side effects (fee, notification), scope (single vs group patient), precondition (confirm: true), and irreversibility. That is everything an agent needs to invoke this destructive tool safely.

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 baseline is 3. The description adds real value by naming the upstream source for reasonId (splose_list_cancellation_reasons) and restating that omitting patient_id cancels the whole appointment, which frames the optional param's blast radius.

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?

Opens with an explicit verb+resource+cardinality ("WRITE: cancels ONE appointment") and names the required inputs. This clearly separates it from splose_update_appointment, splose_get_appointment, and splose_create_appointment without the agent needing to inspect schemas.

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?

Points to splose_list_cancellation_reasons for the required reasonId and gives the exact branching condition for patient_id (group appointments only). It states the confirm requirement and advises confirming with the user first. No explicit 'when not to use' (e.g. reschedule instead of cancel), so not quite a 5.

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