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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: pagination mechanics and the API-key-with-app-access requirement. It doesn't describe result shape in depth, but that is not required here.

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 the resource and its returned fields, and each subsequent sentence adds a filter, pagination, or auth detail. The second sentence ('Lists members the way the Relationship manager does') partly repeats the first, which is the only real waste.

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 an optional-parameter list tool with no output schema, the description covers what is returned, how to filter, how to paginate, and the auth requirement. Only the missing distinction from the export_members sibling keeps it from being fully complete.

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 every parameter is already documented, giving a baseline of 3. The description restates the filter axes and clarifies the cursor round-trip, adding marginal value but nothing the schema doesn't already convey.

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 gives a clear verb+resource (list members) plus the fields returned (tier, status, join date) and filterable dimensions. It does not, however, differentiate from the sibling patreon_export_members, which an agent might reasonably confuse it with, and the 'the way the Relationship manager does' phrasing is more color than disambiguation.

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 states the filter axes (paid/free, active/canceled, tier, join date) and gives concrete pagination guidance ('Pass next_cursor back as cursor for the next page'), plus an auth prerequisite. What's missing is any explicit when-to-use-this-vs-export_members guidance or exclusion, so it stops short of a 5.

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