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

Annotations already mark this as read-only, and the description adds useful behavioral context: it explains the Relay edge/node structure, lists node fields, states the default page size of 50, and warns that the connection is sourced from the community SDK and should be validated against a live account.

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?

The description is front-loaded and appropriately sized, with pagination and the SDK caveat stated early. The final “Memberful GraphQL: subscriptions connection” phrase is slightly redundant with earlier context but not harmful.

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 does the necessary work of describing the return shape as Relay edges with cursor and node fields. Combined with the read-only annotation and pagination guidance, it is complete enough for an agent to invoke the tool correctly.

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 schema already documents all four parameters. The description still adds meaning by explaining the `first` + `after` pagination flow and the non-schema detail that `first` defaults to 50.

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 clearly states a specific verb/resource: listing subscriptions via a Relay connection. It also names the edge/node shape and pagination model. It does not explicitly differentiate itself from sibling tools such as memberful_get_subscription or memberful_graphql.

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 clear pagination guidance using `first` and `after`, including passing the last edge cursor and the default page size. However, it does not say when to use this tool versus alternatives like get_subscription, graphql, or query.

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