removeClientFromClass

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

With no annotations provided, the description bears the full burden of disclosing behavioral traits. It only says 'cancel a booking' but does not mention side effects such as whether it is reversible, triggers a waitlist, affects payments, or how lateCancel behavior works. These are critical omissions for a mutation tool.

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 no wasted words. It states the core function directly, exemplifying conciseness, though it lacks additional context, conciseness as a dimension is about size and structure, and this is exemplary.

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?

The tool has no output schema or annotations, so the description should provide richer context about behavior, return values, or use cases. However, it only gives a one-line purpose, leaving the agent uninformed about the consequences of cancellation, the meaning of the lateCancel parameter, or what response to expect. This is insufficient for a mutation 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?

All three parameters are fully described in the schema (classId, clientId, lateCancel), so the schema coverage is 100%. The description itself adds no parameter-level meaning, but the baseline of 3 is appropriate because the schema already documents the parameters adequately.

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 'Cancel a client's class booking' clearly states the action with a specific verb and resource. It distinguishes from sibling tools like 'addClientToClass' by using 'cancel' rather than 'add', and from viewing tools by the action verb.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without exclusions, prerequisites, or mentions of when not to use it, unlike the get_calls example that names an alternative tool.

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