discord_list_members

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the burden is lighter. The description still adds non-obvious operational context that annotations cannot express: the call fails unless the Server Members Intent is toggled on, which is a genuine prerequisite an agent must know before invoking.

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?

Two short sentences with zero filler; the primary purpose is front-loaded and the prerequisite follows. Nothing is repeated from the title or 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?

For a read-only, three-parameter tool with full schema coverage and no output schema, the definition covers purpose, the optional filter, and the operational prerequisite. Only the shape of returned member records and paging beyond `limit` are unaddressed, which is minor given the schema.

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 `guild_id`, `limit` (1-1000, default 50) and `query` (username/nickname prefix) are already documented. The description only restates that `query` enables name search, adding no format or matching-behavior detail beyond the schema. Baseline 3 for high-coverage schemas.

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 gives a specific verb ('List') and resource ('server members') and adds a second retrieval mode, search by name via `query`. It clearly separates this from write-oriented siblings like discord_moderate_member or discord_member_role, though it doesn't explicitly name a sibling to route against.

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?

It states a real prerequisite — 'Server Members Intent' must be enabled in the Developer Portal — which tells the agent when the call will fail. However there is no guidance on choosing between this and, say, searching members another way, and no mention of pagination or result caps beyond the schema default.

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