List Discord members

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds a genuine behavioral fact — the total result set is capped at 1000, not just per-page — which goes slightly beyond the schema's per-request maximum. It says nothing about pagination mechanics via the cursor or whether results are truncated silently.

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?

One short, front-loaded sentence with zero filler. It is terse to the point of under-specification for a three-parameter paginated tool, but nothing in it is wasted.

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?

An output schema is present, so return values needn't be explained, but with 0% parameter coverage the description leaves the pagination contract (after/limit) undocumented and gives no hint that member listing may be incomplete in large guilds. For a list tool with a cursor, this is not sufficient to call it correctly.

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%, so the description must compensate and it largely does not: guildId is only implied, limit is only alluded to via 'capped at 1000', and the 'after' cursor parameter is never mentioned at all. An agent reading only the description would not know pagination exists.

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 guild members') plus a global result cap, so the operation is immediately identifiable. It does not distinguish itself from the sibling discord_search_members, which is the obvious alternative for the same resource.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. intents/permissions needed to enumerate members), and no reference to discord_search_members as the alternative for filtered lookups. The agent must guess whether this is the right tool for finding a specific member.

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