discord_ban_member

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

With no annotations, the description carries the burden of behavior disclosure. It does reveal an important behavioral gate (confirmation requirement), which is not obvious from the schema. However, it gives no insight into moderation consequences, permission needs, or effects of delete_message_seconds, which are relevant for a destructive moderation tool.

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 concise and front-loaded, delivering the core action in the first sentence and a key condition in the second. It could be slightly clearer about what 'confirmation is enabled' refers to, but overall it is appropriately sized.

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 tool with 5 parameters and 0% schema coverage, the description is too thin. It omits details about the member_id requirement, delete_message_seconds semantics, and the behavior of the ban itself, although the presence of an output schema partially offsets the need to describe return values.

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%, so the description must compensate, but it only clarifies the confirm parameter. Parameters like member_id, reason, guild_id, and delete_message_seconds are left to be inferred from their names and titles, with no added meaning beyond the schema.

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 action 'Ban a member', which is a specific verb and resource. It is clear enough to differentiate from many sibling tools like kick or unban, though it does not explicitly name or differentiate from siblings like discord_unban_member or discord_kick_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 gives a practical invocation requirement: 'Requires confirm=true when confirmation is enabled.' This is a useful when-to-call requirement, but it does not provide any guidance about when to choose banning over alternatives like kicking or timeout, nor any exclusions.

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