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

The annotations already declare readOnlyHint=true, so safety is covered. Beyond the useful gloss that 'standing' means an every-week recurring booking, the description discloses no behavior: no indication whether paused/cancelled standings are included, no ordering, no hint about result size or shape, despite there being no output schema.

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?

It is a single short clause with no redundancy, which is appropriately terse for a simple read tool. However it is a bare noun phrase rather than a front-loaded statement of action and scope, so brevity here reflects under-specification as much as efficiency.

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 one-parameter read-only listing, the description gives the core idea of what is returned (members holding a recurring booking). With no output schema, though, it should still say what a returned member record contains and whether the list is scoped to one class only, which it does not.

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 0% for the single parameter classId, so the description carries the full burden and fails to do so. 'On a class' loosely implies class scoping but never says the parameter is required, nor whether it takes an internal id versus a class name, leaving the agent to guess the format.

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 fragment names the resource implicitly ('Members with a standing booking on a class') but never uses a verb, so the agent must infer 'list' from the tool name alone. The parenthetical defining 'standing' as 'every-week' is genuinely clarifying domain vocabulary. It does nothing to distinguish this from close siblings such as get_gym_class_roster, search_gym_class_members, or list_gym_classes.

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 statement of when to use this versus get_gym_class_roster or search_gym_class_members, which plausibly return overlapping member data for a class. Nor is there any prerequisite or exclusion (e.g. cancelled standings excluded). Usage must be guessed entirely from the name.

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