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

Annotations already declare destructiveHint=true, and the schema already documents that confirm:false returns a preview, so the description mostly restates structured data. It does reinforce the two-phase preview/execute pattern in one line, but adds nothing about reversibility, permissions, or what the preview contains.

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?

Two short clauses, front-loaded with the action and immediately followed by the gating behavior. Zero 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?

No output schema exists, so the description should hint at what the preview returns and whether the cancellation is final or restorable. For a destructive mutation it leaves the standingId provenance and post-cancel state unaddressed, though the confirm gate is covered.

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 50%: 'confirm' is fully described in the schema while 'standingId' has no description anywhere. The description does not explain what a standing ID is or that it comes from list_gym_class_standings, so it fails to compensate for the coverage gap.

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+resource: 'End a member's standing class booking', which is clearly distinct from cancel_gym_class_session (whole session) and create_gym_class_standing. It doesn't name those siblings explicitly, but the resource noun is specific enough for an agent to distinguish them.

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?

There is no when-to-use guidance, no prerequisites, and no naming of alternatives such as cancel_gym_class_session or remove_member_from_gym_class_session. The only contextual cue is the confirm-gating note, which is about invocation mechanics rather than tool selection.

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