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

With annotations present, the description adds substantial context beyond them: it clarifies that removal does not affect the member's plan or billing, that the member loses the spot, that confirmation is on by default but switchable, that the action reaches other people, and that a Cotlet API key with app access is required. That is a rich behavioral disclosure, though it does not describe reversibility or the response.

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?

It is front-loaded with the core action, but the 'PushPress:' prefix and repeated confirmation guidance ('By default you confirm each call... Reaches other people: confirm with the user before each call') restate the same idea twice, adding redundancy that dilutes conciseness.

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 two-parameter removal tool with no output schema, the description covers the effect on the member, the billing/plan non-impact, authorization requirements, and the confirmation flow. It is nearly complete; only edge cases like rebooking or failure behavior are absent.

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% and both parameters are documented (class_id from list_classes, member_id from list_members), so the schema carries the parameter burden. The description adds no syntax or format detail beyond what the schema already provides, making the baseline 3 appropriate.

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 names a specific verb and resource ('Remove a member's reservation or check-in from a class') and clarifies it covers both reservation and check-in removal, echoing the Core UI actions. This distinguishes it from pushpress_book_class_reservation and pushpress_check_in_member without opening a schema.

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?

It gives useful context ('Removes the entry, the same as Remove Reservation or Remove Check-In in Core') and notes 'The member loses the spot,' which implies when this is appropriate. However, it never explicitly compares against alternatives such as pushpress_cancel_class or pushpress_list_no_shows_late_cancels, so usage is only implied rather than stated.

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