Discord Decision MCP

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

With no annotations provided, the description carries full burden. It clearly discloses the destructive nature ('삭제된 메시지는 복구할 수 없습니다' - deleted messages cannot be recovered) and includes a warning symbol (⚠️). However, it doesn't mention authentication requirements, rate limits, error conditions, or what happens with insufficient permissions.

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?

Extremely concise with just two sentences - one stating the purpose, one providing critical warning. Every element earns its place, and the warning is appropriately highlighted with a symbol. No wasted words.

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 2 parameters, 100% schema coverage, and an output schema (though not shown), the description provides the essential warning about irreversibility. However, as a mutation tool with no annotations, it could benefit from mentioning authentication or permission requirements. The existence of an output schema means return values don't need explanation.

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 100%, so the schema already fully documents both parameters (channel_id and message_id). The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high schema coverage.

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 ('삭제한다' - deletes) and resource ('메시지' - message) in Discord. It directly distinguishes from sibling tools like discord_delete_messages (plural) by specifying single message deletion.

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?

No guidance is provided about when to use this tool versus alternatives like discord_delete_messages or other Discord operations. The description doesn't mention prerequisites, permissions needed, or contextual constraints beyond the warning about irreversibility.

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