discord_list_bans

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

No annotations are provided, and the description is minimal. It does not disclose important behavioral traits such as pagination (the 'limit' parameter suggests pagination), permission requirements, rate limits, or what happens on errors (e.g., invalid guild ID).

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 extremely concise at one sentence, but it is under-specified for a useful tool. It lacks structure such as a summary, parameter descriptions, or usage notes. Conciseness here sacrifices necessary detail.

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?

With no output schema and no annotations, the description fails to cover return values, error conditions, or pagination behavior. The tool is a simple list operation, but critical context about how to interpret results is missing.

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 input schema has two parameters ('guildId' and 'limit'), but the description gives no explanation of their meaning or usage. Schema coverage is 0%, so the description adds no value beyond what the schema already provides.

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 'List a guild's bans.' identifies the verb (list) and resource (bans), but does not add specificity beyond the tool name. It fails to distinguish from sibling tools like 'discord_get_ban' or 'discord_unban_user' except implicitly.

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 provides no guidance on when to use this tool versus alternatives such as 'discord_get_ban' for a specific ban or 'discord_ban_user' for creating bans. There is no mention of prerequisites or context.

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