discord_bulk_delete_messages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key constraints: the 2-100 message range, the 14-day age limit, and the permission requirement. However, it does not mention potential side effects (e.g., whether deletions are logged or reversible) or error handling, leaving some behavioral aspects unclear.

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 front-loaded with the core functionality, followed by constraints and usage context. All three sentences are necessary and contribute value without redundancy. It is efficiently structured and appropriately sized for the tool's complexity.

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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description covers essential aspects like purpose, constraints, and permissions. However, it lacks details on return values or error cases, which would enhance completeness. It is mostly adequate but has minor gaps.

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 low (33%), with only 'message_ids' documented. The description compensates by clarifying the purpose of bulk deletion and the 2-100 range, which adds meaning beyond the schema. However, it does not explain 'channel_id' or 'reason' parameters, so some semantic gaps remain.

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 specific action ('Bulk delete'), resource ('messages'), and scope ('from a channel'), distinguishing it from the sibling 'discord_delete_message' which presumably handles single deletions. The verb+resource combination is precise and 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?

The description provides clear context for when to use this tool ('Useful for raid cleanup') and mentions prerequisites ('Requires Manage Messages permission'), but does not explicitly state when NOT to use it or name alternatives (e.g., 'discord_delete_message' for single deletions). The guidance is helpful but not fully comparative.

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