cancel_booking

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

With no annotations, description reveals destructive nature (frees slot, cancels linked meeting, affects guest) and a constraint (cannot cancel if started). Provides sufficient behavioral context.

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 concise sentences: first covers purpose and effect, second adds constraint and prerequisite. No wasted words.

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?

Given single parameter and no output schema, description adequately explains effect and return (updated booking). Lacks mention of auth or permissions, but acceptable for simple tool.

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 has 100% coverage with one parameter; description adds value by directing to list_bookings for obtaining booking_id, which is not in schema.

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?

Description clearly states verb 'cancel' and resource 'booking', and distinguishes from siblings like reschedule_booking. Mentions freeing slot and affecting guest, which differentiates from other actions.

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 explicit usage constraints: cannot cancel if meeting has started, and prerequisite to resolve booking_id via list_bookings. Implicitly suggests confirming intent due to guest impact.

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