Remove a Discord friend or cancel a pending friend request by specifying the user ID to manage your friend list.
Remove a friend or cancel a friend request
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | User ID to remove as friend |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the action but does not specify whether this is a destructive operation, if it requires specific permissions, what happens to the friend relationship (e.g., irreversible removal), or any rate limits. This leaves significant gaps in understanding the tool's behavior.
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 extremely concise—a single, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficient, making it easy to understand at a glance.
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 complexity of a social interaction tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral aspects (e.g., whether removal is permanent), usage context, or what to expect upon execution, making it incomplete for safe and effective use by an AI agent.
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 input schema has 100% description coverage, with the parameter 'userId' clearly documented as 'User ID to remove as friend'. The description does not add any additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating further.
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 ('Remove' or 'cancel') and the resource ('a friend' or 'a friend request'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'discord_get_friends' (which lists friends) or 'discord_add_friend' (which adds friends), though the verb 'remove' inherently contrasts with 'add'.
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, such as whether it's for removing existing friends or canceling pending requests, or any prerequisites like user permissions. It lacks explicit context or exclusions, leaving usage ambiguous beyond the basic action stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.