discord_revoke_permission

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

With no annotations, the description carries full burden. It discloses that the tool reads current permissions and performs a bitwise AND removal, leaving other permissions intact. This is transparent about the mechanism, though it omits potential errors or permission requirements.

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?

Two sentences, zero waste. Directly states purpose and mechanism. No redundant or irrelevant information.

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 no annotations, no output schema, and 0% schema coverage, the description is too brief. It lacks details on return values, error handling, permission prerequisites, and valid permission values. Essential for a mutation tool.

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 coverage is 0%, so description must compensate. It clarifies that 'permissions' are an array of permission names being removed, but fails to describe the format of permission strings, and is inconsistent by mentioning 'by name' while roleId is used. No info on roleId or guildId.

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), the resource (permissions from a role), and that it can handle multiple permissions. It distinguishes from siblings like grant_permission (add) and set_channel_permission (channel-specific). However, it misleadingly says 'by name' while the parameter is roleId, which could cause confusion.

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 on when to use this tool versus alternatives like discord_set_channel_permission or discord_grant_permission. The description does not mention prerequisites (e.g., required permissions) or exclusions.

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