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

Annotations already declare destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine side effect beyond the schema: cancellation notifications are sent to the invitee. However it is silent on whether cancellation is reversible, what happens on a repeat call, and required permissions.

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?

Two short sentences, front-loaded with the action and state scope, followed immediately by the side effect. No filler or repetition of the tool title.

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, but the description does not need to cover return values for a simple cancellation. It covers scope and the notification side effect, which is what an agent needs; minor gaps remain around failure modes and reversibility for a state-changing operation.

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%, so both the id UUID and the optional reason are already documented in the schema. The description adds no format, constraint, or behavioral meaning for either parameter, matching the baseline for full schema coverage.

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 a ... booking') and scopes it to confirmed or pending bookings, which distinguishes it from sibling mutations like neuron_complete_booking or neuron_mark_no_show. It does not explicitly name those siblings, so an agent must infer the boundary from the state constraint alone.

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 'confirmed or pending' qualifier implicitly tells the agent when the tool is applicable, but there is no explicit when-not guidance (e.g., what to do for an already-cancelled or completed booking) and no pointer to neuron_reschedule_booking as the alternative for moving a booking.

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