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

No annotations, so the description carries the full behavioral burden, yet the only disclosure worth noting is '(confirm-gated)' — and the schema's confirm parameter already explains that preview-vs-execute behavior in detail. It says nothing about reversibility, whether scheduled sessions are removed, required permissions, or side effects beyond stopping the class.

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?

A single tight sentence with the key scoping qualifier front-loaded and zero filler. It is efficient, though its brevity borders on under-specification for a mutation tool.

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 destructive-style mutation with no annotations, no output schema, and a 50%-documented parameter set, the description is too thin. An agent cannot tell whether the action is reversible, what happens to already-scheduled sessions, or how classId is obtained.

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 50%: confirm is well documented in the schema, but classId is not described anywhere and the description adds no format, sourcing, or meaning for it. The description fails to compensate for the undocumented half of the parameters.

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?

States a specific verb (stop) and resource (recurring class), and the word 'recurring' meaningfully separates it from cancel_gym_class_session, which acts on a single session. It stops short of naming that sibling directly, so an agent must infer the boundary itself.

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?

Usage is only implied: 'recurring class' hints that this is for whole-series deactivation rather than single-session cancellation, but no alternative tool is named and no condition selects between them. With cancel_gym_class_session, cancel_session, and update_gym_class all in the sibling list, explicit routing would help.

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