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

Annotations already mark this as readOnlyHint=true, and the description adds meaningful behavioral context: it is a Relay connection, it returns cursor-bearing edges, and it warns that the top-level subscriptions connection is sourced from the community SDK and should be validated against a live account. This caveat goes beyond the annotation and helps set expectations about reliability.

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 compact and front-loads the core purpose before pagination details and the caveat. The final 'Memberful GraphQL: subscriptions connection' phrase is slightly redundant with the earlier 'subscriptions connection' mention, but the overall structure is efficient and easy to parse.

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?

Even without an output schema, the description covers the important return shape (edge/node fields), pagination mechanics, defaults, and a reliability caveat. It could also mention interaction between first/last or before/after, but for a read-only listing tool with annotations and full parameter schema coverage, this is a strong and sufficiently complete description.

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, but the description adds real value beyond parameter docs by explaining the default for first (50) and the concrete way to use after ('pass the last edge's cursor'). This makes successful pagination much more likely without requiring the agent to infer cursor semantics.

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 uses a specific verb ('List') and resource ('subscriptions'), and clarifies it is the Relay connection returning edges with cursors and nodes. It clearly differentiates from sibling tools by specifying the top-level subscriptions connection, making it distinct from list_members, list_plans, and get_subscription.

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?

The description gives clear pagination guidance ('Paginate with first + after') and notes the first default of 50, which is useful context. However, it does not explicitly state when to use this tool versus alternatives such as get_subscription or memberful_query, so the agent must infer selection from the tool name and resource type.

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