discord_bulk_delete_messages

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

No annotations are present, so the description carries the behavioral disclosure burden. It does reveal two critical operational constraints (max 100 messages, age cutoff), but the actual destructive behavior of deletion is mainly implied by the name. It does not explain permission requirements, irreversibility, or what the confirm parameter does.

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?

One sentence, zero filler, with the high-value limits placed at the end of a clearly structured phrase. It is concise while preserving the most important rules.

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 deconstructive tool with no annotations and no parameter descriptions, the description leaves too much undefined: an agent cannot know whether it must set confirm to true to actually execute the deleet, or what exactly channel_id/guild_id must target. The output schema exists, which slightly reduces the need to describe return values, but the risky confirm semantics must be disclosed for 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 description coverage is 0%, so the description must compensate almost entirely for parameter meaning. It adds a max message count and age limit, but it does not clarify key inputs like confirm, guild_id, reason, or channel_id beyond what their param names already imply. The confirm flag in particular is unexplained despite being central to a destructive operation.

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 states a very specific verb and resource: bulk-delete messages by ID. It adds concrete limits (max 100, <14 days old), and the phrase 'by ID' clearly separates it from single-message or purge-style tools in the sibling list.

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 makes the intended use case evident: deleting a known set of message IDs. However, it does not explicitly contrast this tool with discord_delete_message or discord_purge_messages, so an agent must infer when this tool should be preferred rather than being told directly.

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