discord_get_role_members

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

Description confirms read-only nature aligning with annotations, and adds output structure details. No annotation contradiction; openWorldHint is not contradicted.

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?

Three concise sentences: action, output format, usage guidance. No redundant words, front-loaded with key information.

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?

Simple read tool with well-described parameters and annotations. Description sufficiently covers output and prerequisite step (discover role IDs). Complete for a list tool.

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 has 100% coverage for both parameters with adequate descriptions. The description adds no new parameter-level details but provides contextual usage advice, meeting baseline for high 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?

Description clearly states 'List every member who currently holds a specific role' and specifies output format (JSON array with id, username, nickname), distinguishing it from siblings like discord_list_members and discord_list_roles.

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?

Explicitly advises to 'Use discord_list_roles to discover role IDs first', providing a clear prerequisite. Read-only hint also guides appropriate usage, though no explicit when-not-to-use is given.

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