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

Annotations already declare readOnlyHint=true, so the agent knows this is a non-mutating read. The description adds useful content-level context (results carry session details and check-in state) and the upstream endpoint, but says nothing about pagination behavior, default result ordering, or what happens when includeCancelled is omitted.

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 sentences, zero filler, with the core purpose front-loaded before the endpoint reference. Nothing needs to be cut or reordered.

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 9-parameter, single-object, read-only list tool with full schema coverage and no output schema, the description covers what the tool returns at a high level and the safety profile is carried by annotations. It is slightly thin on pagination/filter interaction and on how cancelled bookings appear, but nothing essential to invoking it correctly is 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 description coverage is 100%, so every one of the 9 parameters is already documented in the schema, including the date filters, page/pageSize, sortOrder enum, and includeCancelled. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 (List), a specific resource (class/session bookings), and a scope (of one member), plus what the response contains (session details and check-in state). The 'of one member' qualifier implicitly separates it from the sibling momence_list_session_bookings, which lists bookings without a member scope.

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 explicit when-to-use, when-not-to-use, or alternative-selection guidance. The description never mentions sibling tools such as momence_list_member_appointments or momence_list_session_bookings, nor does it state prerequisites (e.g. a valid memberId). Usage is only faintly implied by the scope phrase.

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