discord_delete_channel

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

With no annotations present, the description carries the full burden. It discloses that deletion requires special enabling modes and a confirmation string, which is valuable. However, it does not discuss irreversibility, permissions, what the confirmation string must match, or the effect of the dryRun parameter, leaving significant behavioral details uncovered.

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 a single concise sentence that front-loads the core action ('Delete a channel') and then lists requirements. Every word earns its place, with no redundancy or unnecessary detail.

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 operation with no annotations and no output schema, this description is far from complete. It omits details about execution behavior, return values, error conditions, and the meaning of 'full mode' and 'destructive enablement', leaving a significant context gap.

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?

The schema has 0% description coverage, so the description must explain parameters. It only mentions the confirm parameter ('exact confirmation string'), and does not explain guildId, channelId, dryRun, or reason. The dryRun parameter's default and effect are not described, so parameter semantics are inadequately compensated.

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 uses the specific verb 'Delete' and identifies the resource 'a channel', clearly distinguishing it from siblings like discord_delete_role and discord_upsert_channel. It is unambiguous and directly states the tool's core function.

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 context on when the tool can be used by listing prerequisites (full mode, destructive enablement, exact confirmation string), but it does not explicitly specify when to use this tool versus alternatives or when not to use it. This gives partial guidance without clear exclusions.

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