addClientToClass

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Book' implies a mutation, but it does not explain side effects like payment processing, waitlist handling, capacity checks, or whether the booking can be undone. This is a significant gap for a write operation.

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 a single, front-loaded sentence with minimal words: 'Book a client into a class'. Every word contributes to the core purpose, and there is no redundancy or filler.

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?

Despite rich schema parameter descriptions, the tool overall is under-documented: no output schema, no annotations, and the description omits behavioral expectations such as payment semantics, waitlist behavior, and success/failure responses. For a booking tool with four parameters, this level of context is insufficient.

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 covers all four parameters with descriptions, including waitlist and requirePayment, so schema coverage is 100%. The description adds no further parameter meaning beyond what the schema already provides, earning the baseline score.

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 uses the specific verb 'Book' and names the resource 'a client into a class', clearly stating the tool's core function. It distinguishes from siblings like removeClientFromClass by implying a create/booking action, but it does not explicitly name alternatives or scope.

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 provides no guidance on when to use this tool versus alternatives such as addClientToEnrollment or addClientArrival. It lacks context about prerequisites (e.g., client must exist, class must be open) and gives no exclusions or conditions.

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