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

Annotations only declare readOnlyHint=true, so the description carries the rest of the burden and does so well: it discloses the Relay connection shape, the edge/node payload fields, the default page size of 50, and how cursors chain between calls. It omits ordering/sort behavior and any result-size or rate limits, which keeps it from a 5.

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?

Front-loaded with purpose and payload, then pagination mechanics, then the alternative — a sensible order with dense, non-repetitive sentences. The trailing 'Memberful GraphQL: members connection.' adds little beyond what the first clause already said, a minor bit of filler.

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 minimal annotations, the description compensates by describing the node fields returned and the pagination protocol, which is what an agent needs to call and consume this tool. Missing ordering guarantees and any note on the reverse ('last'/'before') path are the remaining gaps.

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 coverage is 100%, so the baseline is 3; the description earns above that by explaining the cursor-chaining relationship between 'after' and an edge's 'cursor' and by stating that 'first' defaults to 50 — a default not present in the schema. It says nothing about 'last'/'before' semantics or the 1–1000 bounds, leaving reverse pagination to the schema.

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 members') and immediately characterizes the return payload (cursor + node with profile, Stripe customer id, unrestricted-access flag, total spend, subscriptions). It also names the sibling it is not ('For member-state filters beyond active, use memberful_query'), so an agent can route correctly without opening a schema.

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 explicit pagination guidance ('first' + 'after', pass the last edge's cursor) and an explicit alternative with its triggering condition (memberful_query for non-active member-state filters). It does not cover the single-member case (memberful_get_member) or when to prefer listing subscriptions instead, so it falls short of fully exhaustive routing guidance.

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