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

The readOnlyHint annotation already establishes the safe-read profile, so the description's added value is the disclosure of what is actually returned: active subscriptions and class packs with type, dates, credits left, usage limits, and freeze state. That is genuinely useful given there is no output schema. It doesn't cover pagination behavior, but the schema does.

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 dense sentence front-loads the scope and then the returned fields, followed by the underlying endpoint. No filler, though the field list makes the single sentence fairly heavy.

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, the description compensates by naming the returned fields, and the schema fully covers the four parameters. An agent has enough to call it correctly; only explicit sibling routing and pagination semantics are absent, and pagination is covered by the schema.

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 memberId, page, pageSize, and includeFrozen are all documented in the schema. The description only alludes to the scope ('active') and freeze state, adding no format or constraint detail beyond the schema, matching the baseline 3.

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 scoped resource (one member's active subscriptions and class packs), and it enumerates the fields returned (type, dates, credits, usage limits, freeze state). It scopes to a single member, which implicitly separates it from momence_list_memberships, but it never names or contrasts with a sibling explicitly.

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 'one member's active...' — you call it when you have a memberId and want that member's current bought memberships. There is no statement of when not to use it, no mention of the sibling momence_list_memberships, and no prerequisites such as required permissions.

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