cancel_next_wake

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

With no annotations, the description carries the full behavioral burden. It usefully discloses several things the tool does NOT cancel, which is meaningful context, but it does not say whether cancellation is idempotent, what permissions are needed, what happens if the appointment is missing, or what side effects occur.

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 and front-loads the core action before the exclusions. It is efficient, though the phrase 'your named appointment' is slightly awkward against the tool name's 'wake' terminology.

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?

An output schema exists, so return values need not be explained. Still, for a mutation tool with no annotations and 0% parameter description coverage, the description leaves important gaps around the required reason field, permissions, and cancellation side effects.

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 0%, so the description must compensate. It explains the optional 'name' parameter and its default, but the required 'reason' parameter is never described at all, leaving a required input undocumented in both schema and description.

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 gives a specific verb, 'Cancel', applied to 'your named appointment', with a default when the name is omitted. It is distinguishable in practice from the sibling schedule_next_wake, though it never names that sibling and uses 'appointment' instead of the tool name's 'wake'.

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 description supplies a when-not list ('does not recall an in-flight or accepted batch, interrupt a turn, or clear an uncertainty hold') and mentions the default name behavior. However, it does not explicitly route the agent to schedule_next_wake, iam_timer_cancel, or another sibling for the excluded cases.

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