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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds useful framing (these are appointment reservations / 1:1 services) plus the underlying API endpoint, but omits behavioral traits such as whether cancelled appointments are excluded by default and pagination/default-page behavior. Modest value beyond annotations.

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 tight sentences with the resource and scope front-loaded; the endpoint reference is borderline redundant but compact. No filler or repetition.

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?

A read-only list tool with no output schema, but full schema-description coverage and a clear safety annotation. The description plus structured fields give the agent enough to invoke correctly; a note on default cancelled-exclusion behavior would complete it.

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 the schema itself documents all 9 parameters including the date filters, pagination, sort, and includeCancelled. The description adds nothing parameter-specific, so the baseline 3 for schema-covered params 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 precise resource (appointment reservations / 1:1 services), and a scope (of one member). The 'of one member' scoping implicitly distinguishes it from the sibling momence_list_appointments, though that sibling is never named. An agent can infer the difference, but explicit differentiation is absent.

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?

Usage is implied by the 'of one member' scoping — you reach for this when you want a single member's appointments rather than all appointments. However, no explicit when-to-use, when-not-to-use, or alternatives (momence_list_appointments, momence_list_member_session_bookings) are provided. This is minimum-viable implied guidance.

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