discord_unban_member

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description's note about needing 'Ban Members' permission adds useful context beyond the annotations. However, it doesn't clarify what 'Confirmation' means as a return value—the output schema may cover that, but the description is thin on behavioral detail beyond the permission requirement.

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?

Extremely concise: one sentence for the purpose and one for the permission requirement, plus a brief return note. Front-loaded and waste-free.

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 mutation tool with an output schema and annotations, the description covers the core action and permission requirement minimally. It lacks details on error handling (e.g., if user isn't banned), audit logging behavior for the reason parameter, or any caveats, leaving gaps that could affect correct invocation.

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 67%, with user_id having no description but reason and guild_id documented in the schema. The description doesn't add parameter information beyond what's in the schema. Baseline 3 is appropriate given partial schema coverage and no supplementary parameter semantics in the description.

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+resource: 'Lift a ban so the user can rejoin.' Clearly distinguishable from siblings like discord_ban_member and discord_kick_member. The 'Returns: Confirmation' line adds little but doesn't detract.

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 implies a prerequisite ('Needs Ban Members') but doesn't explicitly say when to use this versus alternatives, or when-not to use it (e.g., for timed bans versus permanent bans). Usage is implied rather than spelled out.

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