discord_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 of behavioral disclosure. It effectively describes key behaviors: it's a read operation (implied by 'List'), requires specific permissions ('Server Members privileged intent'), and supports pagination ('Paginate with `after` cursor'). However, it lacks details on rate limits, error conditions, or response format.

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 front-loaded with the core purpose, followed by essential details (pagination and permission requirement) in two concise sentences. Every sentence earns its place with no wasted words, making it highly efficient and well-structured.

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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is mostly complete. It covers purpose, pagination, and permissions, but lacks details on response format, error handling, or rate limits. For a list operation with no output schema, this is adequate but not exhaustive.

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 67% (2 out of 3 parameters have descriptions). The description adds value by explaining the pagination mechanism ('after cursor (last user ID)'), which clarifies the schema's 'after' parameter. However, it does not provide additional context for 'guild_id' or 'limit' beyond what the schema offers, meeting the baseline for moderate coverage.

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 verb ('List') and resource ('members of a guild'), making the purpose specific and unambiguous. It distinguishes from siblings like 'discord_get_member' (singular) and 'discord_list_guilds' (different resource), providing clear differentiation.

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 explicitly states when to use this tool ('List members of a guild') and provides context for pagination, but does not specify when not to use it or name alternatives among siblings. It mentions a prerequisite ('Requires the Server Members privileged intent on the bot'), which is helpful guidance.

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