discord_list_bans

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

Annotations already declare readOnlyHint: true, and the description confirms it's read-only. The description adds valuable behavioral context about pagination: 'A page holds up to 1000 bans; if nextCursor is non-null, pass it back as `after` to fetch the next page.' This goes beyond annotations. No contradiction.

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 two sentences and zero waste. The first sentence states the purpose; the second handles pagination and permissions. Every sentence 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?

Given the schema coverage (100%) and output schema presence, the description is complete. It explains pagination, required permissions, and return format. There are no gaps for a list tool.

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?

The schema covers all parameters with descriptions (100% coverage). The description adds context beyond the schema by explaining the pagination flow ('pass it back as `after`') and the guild_id parameter is clear from context. The parameter descriptions in the schema are detailed (pattern, default, min/max), so the description provides extra operational guidance.

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 clearly states the tool's purpose: 'List the users banned from the server, with their ban reasons.' It uses a specific verb and resource, and the return shape ('returns { bans: [...], nextCursor }') clarifies what the tool provides. It distinguishes itself from sibling tools like discord_ban_member and discord_unban_member.

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?

The description explicitly mentions the required permission ('Requires the Ban Members permission'), which helps the agent know prerequisites. It also clarifies the tool is read-only. However, it does not explicitly contrast with alternatives or state when not to use it, which is a minor gap.

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