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

Goes well past the annotations by disclosing what destruction actually means here (series scope cancels every later occurrence), the connection-level authorization restriction that differs from the workspace role, and the untrusted-data handling contract. It does not say whether a cancellation can be undone or whether attendees are notified, which is the remaining behavioral gap for a destructive tool.

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 core action, then authorization, then scope semantics, then the injection warning — every sentence carries information. The untrusted-key note is generic boilerplate but is security-relevant enough to justify its place.

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?

Covers authorization, destructive scope, and data-trust concerns for a 3-parameter mutation tool with no output schema. It omits what a successful call returns or how a partially-invalid series is handled, a minor gap given the destructive nature.

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 67% and the description's explanation of "series" mostly restates the enum description, though it adds the useful constraint that it must be passed on an occurrence of a repeating booking. reservationId is left undocumented in both schema and description, so no compensation for the coverage gap.

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 and resource ("Cancel your own upcoming reservation") and immediately extends scope with the series variant, so an agent can distinguish it from modify_reservation or list_my_reservations without opening the 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?

Explicit about who may use it (own bookings; workspace admins/owners may cancel any), when the series scope applies (passing "series" on an occurrence of a repeating booking), and the one exception that overrides the admin rule (admin override enabled on the AI assistants page), plus the tool to check it with (get_workspace_info).

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