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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds substantial context beyond them: the visit's post-state (COMPLETE + CANCELLED tag, record retained), and the non-obvious nuance that suppressing notifications may not stop scheduled reminders/follow-ups. That notification caveat is exactly the kind of behavioral detail annotations cannot convey.

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 operation type and scope, and the endpoint is placed last. It is efficient overall, though the notification-suppression caveat is stated twice across description and schema, costing some 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?

For a two-parameter cancel operation with no output schema, the description covers scope (one visit), side effects (state/tag, record retention), notification behavior, and the HTTP path. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100% and the send_notifications property already documents the suppression caveat in near-identical wording, so the description's restatement adds little. It does not add syntax or format meaning for visit_id beyond what the schema states.

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 (cancel) and resource (ONE visit, waitlist entry or booking) plus the resulting state change (COMPLETE + CANCELLED tag, not deleted). An agent can distinguish this from waitwhile_update_visit or a hypothetical delete without opening either schema.

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?

The 'WRITE:' prefix and 'cancel ONE visit' framing make the write context clear, and the clarification that the visit is kept rather than deleted correctly disambiguates it from a destructive-delete intent. However, it never names an alternative (e.g. update_visit for rescheduling) or states when cancellation is inappropriate.

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