discord_list_members

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

There are no annotations, so the description carries the transparency burden. It does add a meaningful behavioral caveat—the need for the Server Members Intent—and implies a read-only operation. However, it does not disclose pagination, rate limits, or which members are included, so the extra context is useful but limited.

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 one short sentence with no filler, and the most operationally important caveat is placed right in the sentence. Every word 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?

The tool is low-complexity and has an output schema, so return-value prose is unnecessary. Still, for an agent invoking the tool, the optional/nullable guild_id and limit semantics are not explained, which leaves a non-trivial completeness gap. Overall it is minimally usable but not fully complete.

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 0%, and the description only vaguely maps to guild_id through 'in a guild' while saying nothing about limit. It does not explain that guild_id is optional/nullable or what limit controls, so the description fails to compensate for the schema's gaps.

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 phrase 'List members in a guild' names a specific verb and resource, and 'guild' clarifies the scope. It is clearly distinct from 'get member' or 'search members' in the sibling list, though it does not explicitly call out any sibling 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?

No when-to-use or when-not-to-use guidance is provided. The Server Members Intent note is a prerequisite, not a selection rule, and the description does not contrast with discord_get_member or discord_search_members.

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