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

Annotations already confirm readOnlyHint=true, so safety is covered; the description adds return-shape disclosure (booking id, member, check-in state, recurring-booking id), which is genuinely useful given there is no output schema. It stops short of describing pagination behavior or how cancelled bookings appear when includeCancelled is set.

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?

One front-loaded sentence carries the purpose and the return contents, followed by a compact endpoint reference. No filler or restatement of the name.

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?

With six fully documented parameters and no output schema, the description fills the main gap by naming the fields each booking row contains. Only minor gaps remain — no note on pagination shape or how the cancelled-booking option affects results.

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 100%, so page, pageSize, sortBy, sortOrder and includeCancelled are already fully documented in the schema. The description adds only the notion of a single session scope, which the schema's sessionId entry already conveys — baseline 3 is 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?

Specific verb (list) plus a tightly scoped resource ('who is booked into one session — the class roster') and an enumeration of the returned fields. The phrase 'one session' implicitly separates it from the sibling momence_list_member_session_bookings, which pivots on the member rather than the session.

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?

The session-scoped framing implies when the tool applies, but the description never states when to prefer it over momence_list_member_session_bookings or momence_get_session, nor does it mention any prerequisites or exclusions. Usage is inferable rather than stated.

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