Reservar clase

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

With no annotations, the description carries the full burden. It discloses the waiting-list behavior via insist=true and the disambiguation logic, but doesn't mention important traits like idempotency, confirmation responses, or authorization requirements. Some transparency is present, but not comprehensive.

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?

Three sentences, each earning its place: action, identification method, disambiguation rule, and waiting-list option. No filler or redundancy.

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 6 optional parameters and no output schema, the description covers the main booking flow and edge cases (multiple classes, full class). It omits return-value details and prerequisites, but for a booking tool the core behaviors are addressed.

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 100%, so the baseline is 3. The description adds value by explaining how parameters relate: time or classId for identification, name for disambiguation, insist for waiting list. This clarifies semantics beyond the individual schema descriptions.

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 opens with 'Reserva una clase' (Book a class), a clear verb+resource statement. It distinguishes from siblings like cancel_class and list_classes by specifying the booking action and how to identify the class (time or classId).

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 concrete usage guidance: identify by start time or classId, add 'name' to disambiguate when multiple classes overlap, and use insist=true for waiting list. It doesn't explicitly exclude alternatives but gives clear context for when to use the tool and how to handle ambiguity.

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