discord_get_role_members

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

Annotations already cover the read-only/open-world profile, but the description adds genuinely new behavioral facts: a hard scan ceiling of 20,000 members, the return envelope { members, truncated }, and the instruction to inspect `truncated` on large servers. That truncation semantics is exactly the kind of operational detail annotations cannot convey.

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 short sentences, front-loaded with the action and scope, followed by the return/truncation caveat and the prerequisite. No filler and nothing repeated from the schema.

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 an output schema and fully documented parameters, the description only needs to add the behavioral caveats, and it does: the 20,000 cap, the truncated flag, and the role-ID discovery step. Nothing an agent needs to call this correctly is missing.

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% and both parameters carry snowflake patterns and descriptions, so the schema does the heavy lifting. The description only implies that role_id selects the filter and says nothing about guild_id or ID format beyond what the schema already states, so 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 and resource ('List members who currently hold a specific role') and is clearly separable from the sibling discord_list_members, which lists all members rather than role holders. An agent can pick between the two without opening either schema.

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 instructs the agent to use discord_list_roles to discover role IDs first, which is a real prerequisite because role_id is a snowflake. It does not state when to prefer discord_list_members plus manual filtering or note any permission caveats, but the primary routing guidance is present.

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