Cancelar reserva

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions that late cancellation may incur a penalty depending on the box, which is a meaningful side effect. However, it does not describe other outcomes like confirmation or reversibility, but the primary effect (cancellation) is clear.

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 concise—two sentences that are front-loaded with the core action and followed by essential usage details. There is no redundancy or filler, and every word contributes to the agent's understanding.

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 the tool has six optional parameters and no output schema, the description is reasonably complete. It covers the main usage scenario (identifying and canceling a reservation) and mentions the late penalty. However, it does not explicitly state that at least one of time or classId is required, and it does not hint at the response format. These minor gaps are partially mitigated by the schema's parameter descriptions.

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?

The input schema already provides full descriptions for all six parameters (100% coverage). The description adds value by linking parameters together: it explains that you can identify the reservation via 'time' or 'classId', and clarifies the purpose of 'late'. This goes beyond the schema's individual parameter definitions.

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 the action: 'Cancela tu reserva en una clase' (Cancel your reservation in a class). It also specifies how to identify the reservation (by start time or classId), making it distinct from sibling tools like book_class. The verb and resource are unambiguous.

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 gives practical usage instructions: identify the reservation by start time or classId, and use late=true for cancellations outside the deadline. It does not explicitly compare with alternatives, but the context of a cancellation tool alongside book_class makes the use case clear.

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