discord_list_bans

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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only' is redundant but consistent. Beyond that, the description discloses the 1000-item page ceiling, the nextCursor-to-`after` loop, and the required Ban Members permission — genuinely useful behavioral context an agent could not infer from the schema alone.

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?

Four short sentences, front-loaded with purpose, then return shape, pagination mechanics, and the permission gate. No filler and nothing repeated except the brief 'Read-only' confirmation.

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 3-parameter read tool with an output schema, the description covers what an agent needs: scope, page size, cursor loop, and permission requirement. Return-value detail can safely be left to the output 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 coverage is 100%, so the baseline is 3; the description adds meaning by explicitly linking the response's nextCursor to the `after` parameter, which is the only non-obvious parameter relationship. `limit` and `guild_id` are left to the schema, which already documents them well.

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?

Specific verb+resource (list banned users) plus what the payload contains (ban reasons). It is clearly distinguishable from the sibling mutations discord_ban_member, discord_unban_member and discord_bulk_ban without opening any 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?

States the operational precondition (Requires the Ban Members permission) and the pagination condition for repeat calls, which tells the agent when and how to invoke it. It does not explicitly route away from siblings such as discord_get_audit_log or discord_search_members for ban-related lookups, so it stops short of full when/when-not guidance.

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