List members

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

With no annotations provided, the description carries the full burden. It discloses pagination, email masking (a data transformation trait), optional tier filtering, and the members:read scope requirement. It does not describe the response structure or error/rate-limit behavior, but for a list operation these are less critical. The masking and scope details go beyond the schema, providing useful behavioral transparency.

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 two sentences and efficiently conveys core functionality, pagination, masking, filtering, and auth. No redundant words; every clause adds information. It is front-loaded with the main verb and resource.

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 a list tool with no output schema or annotations, the description covers purpose, pagination, filtering, masking, and auth. However, it does not describe the response format (e.g., array of members with pagination metadata), which would be helpful given no output schema exists. The description is helpful but not fully complete in this dimension.

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?

The schema already provides complete descriptions for all three parameters (page, tier, perPage) with defaults, ranges, and enum values. Schema coverage is 100%. The description mentions tier filtering and pagination but does not add new parameter-specific semantics beyond the schema, so the baseline of 3 applies.

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 the tool's function: 'Lists reader/subscriber records, paginated.' It provides a specific verb (lists), resource (reader/subscriber records), and key contextual details (email masking, tier filter, required scope). The resource is unique among siblings (members vs posts/media/comments), so it distinguishes itself effectively.

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 clearly indicates this is for listing reader/subscriber records, implying use when member data is needed. It mentions the optional tier filter and required scope, giving context. However, it does not explicitly compare to sibling list tools (e.g., 'for posts use list_posts'), so it lacks explicit exclusions or alternatives. Usage context is clear but not exhaustive.

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