discord-mcp

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action is destructive ('Delete'), but doesn't clarify if deletion is permanent, reversible, or has side effects (e.g., notifying users, affecting linked content). No rate limits, authentication needs, or error conditions are mentioned.

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—one sentence with zero wasted words. The parenthetical '(close)' efficiently clarifies terminology without verbosity. It's front-loaded with the core action and target.

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 tool with no annotations, 0% schema coverage, and no output schema, the description is inadequate. It lacks essential context: permissions required, whether deletion is permanent, what happens to replies, error scenarios, or return values. Siblings like 'discord_update_forum_post' suggest alternatives, but no guidance is given.

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 adds no parameter information. It doesn't explain what 'thread_id' represents, how to obtain it, or its format (e.g., numeric ID vs. string). The single parameter remains semantically opaque beyond the schema's type constraint.

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 ('Delete') and target ('forum post/thread'), with the parenthetical '(close)' providing useful semantic clarification. It distinguishes from siblings like 'discord_delete_message' by specifying forum posts/threads, though it doesn't explicitly contrast with 'discord_update_forum_post' or 'discord_reply_to_forum'.

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_update_forum_post' (which might archive or lock instead) or 'discord_delete_channel' (for broader deletion). The description doesn't mention prerequisites (e.g., permissions) or typical use cases (e.g., moderation).

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