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

Adds substantial behavior beyond annotations: it records a reason, affects the client's booking (a side effect), requires per-call confirmation by default, reaches other people, and needs a Cotlet API key with app access. This is exactly the kind of side-effect, auth, and confirmation disclosure annotations cannot carry.

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-loads the action and constraint well, though the confirmation guidance is somewhat repetitive ('confirm it', 'you confirm each call', 'confirm with the user before each call'), costing a little efficiency.

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-param mutation with no output schema, the description covers side effects, confirmation policy, auth requirements, and cross-person impact. Nothing essential is missing, though it could clarify the result of a successful cancel.

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% and the description largely repeats the schema's own note that reason is set up at the location. It adds the constraint that the reason must already exist, but no syntax or format detail beyond the structured field.

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 (appointment) plus the scope 'one appointment' and the required reason capture. An agent can distinguish this from meevo_reschedule_appointment or meevo_book_appointment without opening any 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?

Provides contextual guidance (reason must be configured at the location, confirm before calling) but never names or contrasts alternatives such as reschedule. Usage conditions are implied rather than explicitly routed.

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