discord_list_members

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

Annotations already declare readOnlyHint and openWorldHint, and the description reinforces read-only while adding genuinely new behavioral facts: page capacity of 1000, ordering by user ID, and the exact cursor round-trip rule. It stops short of mentioning permission/intent requirements (e.g. privileged member-listing access), which is the one material omission for a paginated enumeration call.

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?

Four short sentences, front-loaded with purpose, then return shape, then pagination mechanics, then alternatives. Every sentence carries information an agent needs; there is no filler.

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 though an output schema exists and the return shape could be left implicit, the description still summarizes it and explains the cursor contract. Combined with the annotations and full schema coverage, an agent has everything needed to call and paginate 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 all three parameters are already documented in the schema, including the default of 50 and the 1–1000 range. The description's pagination sentence mostly restates what the `after` parameter description already says, so it adds little beyond the schema baseline.

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 and resource ('List members of a server') plus the notable scope details (includes roles, ordered by user ID). It explicitly differentiates itself from discord_search_members and discord_get_member_info, so an agent can pick it without opening the schemas.

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?

Names two alternatives with the condition that selects each: search_members for name lookups, get_member_info for a single member's full details. It also gives the concrete pagination procedure (pass nextCursor back as `after`), leaving nothing to inference.

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