Discord MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'clean up' implies deletion/removal, it doesn't specify whether this is reversible, what permissions are required, whether it affects the original Discord server content, or what happens if the file doesn't exist. For a tool that likely performs file system operations, this is insufficient behavioral context.

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 that gets straight to the point. Every word serves a purpose - 'Clean up' (action), 'previously downloaded' (context), 'Discord attachment file' (resource). There's no wasted verbiage or unnecessary elaboration.

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 tool that performs file cleanup operations with no annotations and no output schema, the description is too minimal. It doesn't explain what 'clean up' means operationally (delete? move to trash?), what happens on success/failure, or any side effects. Given the potential for destructive file operations, more context is needed.

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% with the single 'path' parameter well-documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema (which states 'File path to clean up'). This meets the baseline expectation when schema coverage is complete.

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 ('Clean up') and the target ('a previously downloaded Discord attachment file'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'discord_delete_message' or 'discord_remove_reaction' which also involve cleanup/deletion operations, though the specific resource type (attachment file) provides some distinction.

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 minimal guidance - it mentions 'previously downloaded' which implies a prerequisite but doesn't specify when to use this tool versus alternatives. There's no explicit 'when-not' guidance or comparison to sibling tools like 'discord_delete_message' for message cleanup versus file cleanup.

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