discord_delete_channel

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

With no annotations provided, the description carries full burden but only mentions an 'optional reason' parameter. It fails to disclose critical behavioral traits: this is a destructive operation (permanent deletion), likely requires specific permissions (e.g., admin rights), may have rate limits, and doesn't describe what happens upon success/failure (e.g., confirmation message or error).

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, efficient sentence with zero wasted words. It's front-loaded with the core action and includes a useful detail about the optional parameter, making it appropriately concise 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 destructive nature, no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks essential context: permissions required, irreversible consequences, error handling, and comparison to sibling deletion tools, making it inadequate for safe and effective use.

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 only adds minimal context: it notes 'reason' is optional. It doesn't explain 'channelId' format (e.g., numeric ID) or provide examples, leaving parameters largely undocumented. This meets the baseline for inadequate compensation.

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 ('Deletes') and resource ('a Discord channel'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'discord_delete_category' or 'discord_delete_message', which perform similar deletion operations on different resources, so it doesn't reach the highest score.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing admin permissions), exclusions (e.g., cannot delete default channels), or compare it to siblings like 'discord_delete_category' for context-specific choices.

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