cancel_cab

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Cancel', implying a state change, but does not describe side effects (e.g., refunds, reversibility), permissions required, rate limits, or endpoint behavior. The output schema exists but is not referenced to clarify return values.

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 extremely concise: one line for purpose, then a docstring-style argument list. Every sentence adds value, no fluff. The key information is front-loaded.

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 simple tool with 2 parameters and an output schema, the description covers the basic purpose and parameter sources. However, it lacks details on error handling, idempotency, or response structure, which are helpful for an agent to fully understand the tool's behavior.

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%, but the description adds essential meaning: booking_id is the trip ID from list_cab_bookings, and reason is optional. This clarifies the source and intent of parameters beyond the bare 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?

The description clearly states 'Cancel an office cab booking', specifying the verb (cancel) and the resource (cab booking). This distinguishes it from siblings like cancel_lunch and book_cab, which are different tools for different actions or resources.

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 explains that the booking_id comes from list_cab_bookings, giving clear context on the prerequisite. However, it does not explicitly state when not to use this tool (e.g., if the booking is already cancelled) or provide alternatives beyond the sibling tool context.

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