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

readOnlyHint=true already establishes the operation is a safe read, so the description only needs to add context — which it does by disclosing the shape of the returned data (visit counts, custom fields, tags) and the underlying endpoint. Pagination and rate-limit behavior are not mentioned, but the schema covers paging.

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 short sentences, front-loaded with purpose and then the two most decision-relevant parameters. The trailing 'Momence: GET /api/v2/host/members' is minor noise that does not help tool selection.

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 no output schema and seven optional parameters, the description usefully summarizes the returned fields and the two filter entry points. It is nearly complete for a read-only list tool, missing only guidance on default ordering and result volume.

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% and every parameter is self-documented, so the baseline is 3. The description restates the semantics of `query` and `filterPreset` rather than adding new meaning, and says nothing about sortBy, sortOrder, staticSegmentId or pageSize.

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 states a specific verb and resource ('List or search the studio's customers (members)') and even names the fields returned (visit counts, custom fields, tags). It is clearly the bulk-listing counterpart to the singular momence_get_member, though it never names that sibling to make the distinction explicit.

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 concrete conditions for two parameters ('Search by name, email or phone with `query`', 'use filterPreset=with-active-membership for current members'), which tells the agent when to reach for them. It stops short of naming alternatives such as momence_get_member for a single record or the segment-based filtering path.

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