unban_member

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the bare action. It does not say what happens if the user is not currently banned, whether required permissions or role hierarchy checks apply, or what the response contains. Only the mutating nature of the operation is conveyed, and that comes mostly from the tool name.

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 single short sentence is front-loaded and free of padding, which is structurally sound. But its brevity reflects under-specification rather than efficiency, and the encoding corruption makes the one sentence it does have less useful.

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, permission-gated mutation with three undocumented parameters, no annotations, and no output schema, the definition supplies almost nothing an agent needs to call it safely. There is no information on side effects, failure modes, or return values, leaving the definition fundamentally inadequate for this tool's complexity.

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% across all three parameters, and the description adds no meaning for guild_id, user_id, or the optional reason. An agent gets no signal about ID formats, whether reason is shown in the audit log, or how guild and user identifiers relate.

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 sentence names a concrete verb and resource (removing a ban from a user), so the basic operation is inferable. However, it is a single generic phrase that never mentions the guild scope implied by the required guild_id, and the text is corrupted by mojibake ('usuário') and written in a different language than the tool name and siblings, which weakens clarity. No differentiation from ban_member or kick_member is offered.

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 tool versus ban_member, kick_member, or timeout_member, and no statement of prerequisites such as the bot needing ban permissions or the target actually being banned. The agent must infer the entire usage context 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.