discord_remove_role

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

With no annotations, the description must disclose behavioral traits. It only states the action and permission, omitting important details such as whether the operation is destructive, rate limits, side effects, or the role of the 'confirm' parameter. This leaves the agent underinformed.

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 sentence, which is concise and front-loaded. However, it omits critical context, so while it is brief, it sacrifices completeness for brevity.

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 has 5 parameters, limited schema coverage, no output schema, and no annotations, the description is incomplete. It lacks details about return value, the necessity of the 'confirm' parameter, and potential side effects, making it insufficient for safe invocation.

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 only 20% (only 'confirm' described). The description adds no additional meaning to the parameters; it does not explain 'guildId', 'userId', 'roleId', or 'reason'. Since coverage is low, the description fails to compensate.

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 a role from a member.' It identifies the resource (role) and the action (remove). However, it doesn't explicitly differentiate from sibling tools like discord_add_role, though the verb 'remove' distinguishes it.

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 mentions the required permission 'requires Manage Roles,' which is a prerequisite. However, it provides no explicit guidance on when to use this tool versus alternatives (e.g., discord_add_role, discord_delete_role) or when not to use it.

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