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

Annotations only supply destructiveHint=true, so the description carries most of the load: it discloses the membership-selection behavior on waitlist conversion, the useBoughtMembershipIds override condition, and the returned waitlistBookingId. It does not state auth or rate-limit needs, keeping it short of a 5.

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?

Three tight sentences, front-loaded with the action and followed by the conditional behavior and return value. The trailing REST endpoint is mildly extraneous but not wasteful.

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 3-parameter mutation with no output schema, the description covers the action, the conditional membership behavior, and the return value (waitlistBookingId). It is complete enough to call correctly, with only auth/permission context missing.

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%, so the baseline is 3, but the description adds real meaning for useBoughtMembershipIds: without it Momence picks the best matching bought membership, with it those specific memberships are tried. That is behavior the schema's terse 'Bought memberships to try' does not convey.

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 and resource ('Put a member on a session's waitlist') that clearly distinguishes it from sibling booking tools like momence_book_member_free and momence_cancel_session_booking.

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 implies when the tool applies by explaining the downstream waitlist-booking flow, but never states when to use this versus booking directly or how it relates to sibling tools. Usage is inferable rather than explicit.

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