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

Annotations declare readOnlyHint=true, so the safety profile is covered, and the description adds meaningful behavioral detail by disclosing the return shape (edges[].node with role, pageInfo, totalCount). It also correctly notes offset-based pagination, though it doesn't cover rate limits or result-set caps.

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?

Compact and front-loaded: purpose first, then filters, then return shape. The trailing 'Bettermode GraphQL query: members.' is mildly redundant but harmless for agents mapping to the underlying API.

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 steps up to document the response envelope (edges[].node, pageInfo, totalCount) and pagination model, which is exactly what's needed. Only minor gaps remain around permissions or total-count edge cases.

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 all six parameters are already documented (including the name/username/email match semantics for query). The description restates those filters but adds no syntax, default, or constraint information beyond the schema, so the baseline 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?

States a specific verb (List) and resource (members of the community) with scope (pagination, optional filters). It clearly differentiates from sibling list tools by naming the resource, though it never explicitly contrasts with bettermode_get_member for single-member retrieval.

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 implies usage through the filter options (search, role, order, reverse) but gives no explicit when-to-use versus when-not, and does not route the agent to bettermode_get_member or bettermode_search. Guidance is inferable rather than stated.

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