Unban Discord member

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no mention of the required Ban Members permission, whether the reason is written to the audit log, or what the 'confirm' flag gates.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity is under-specification rather than discipline, which is penalized in the other dimensions.

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 destructive, open-world mutation with a confirm flag, the definition omits permission requirements, confirm semantics, and audit-log behavior for the reason field. The output schema covers return values, but the operational preconditions an agent needs before invoking it are 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?

Schema description coverage is 0% for 4 parameters. The description implicitly maps to guildId and userId but says nothing about 'reason' (audit-log text, 512-char limit) or 'confirm' (presumably a safety gate for a destructive action), leaving half the parameters undocumented in both places.

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 ('Remove') and resource ('guild ban for a user'), which distinguishes it from the sibling mutation tools discord_ban_member and discord_kick_member. It does not explicitly name those siblings as alternatives, but the intent is unambiguous.

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 guidance on when to use this versus discord_ban_member, discord_kick_member, or discord_bulk_ban_members, nor on prerequisites such as the user currently being banned or required permissions. The agent must infer all of this from the name alone.

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