discord_list_members

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

The description discloses read-only behavior, pagination mechanism, maximum page size (1000), and ordering by user ID. Annotations already indicate readOnlyHint: true and openWorldHint: true, and the description reinforces these without contradiction. Full behavioral context is provided.

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 three sentences: clear purpose, pagination details, and alternatives. It is front-loaded with the action and result shape. No redundant information; every sentence earns its place.

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?

Despite lacking an output schema, the description specifies the return shape ({ members: [...], nextCursor }) and explains pagination fully. It covers ordering, page size limits, and indicates read-only nature. For a list operation, this is complete and sufficient.

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 each parameter is already documented in the schema. The description adds value by explaining the pagination cursor ('after') in context, linking it to the response's nextCursor, and noting default limit. This contextualizes the parameters beyond the basic schema descriptions.

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 'List members of a server with their roles, ordered by user ID.' It specifies the verb (list), resource (members), and includes ordering and roles. It also explicitly differentiates from sibling tools, mentioning discord_search_members for specific members and discord_get_member_info for a single member's details.

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 provides explicit when-to-use vs alternatives: 'Use discord_search_members to find specific members by name, or discord_get_member_info for one member's full details.' It also covers pagination usage: 'pass it back as `after` to fetch the next page.' The read-only hint clarifies appropriate usage context.

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