remove_role

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

With no annotations, the description carries the full burden. It discloses permission requirements and the bot role hierarchy check, but does not describe return behavior, error conditions, or side effects beyond the role removal itself. Some behavioral context is present, but gaps remain.

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, front-loaded sentence with no filler or redundancy. Every word contributes to the action and prerequisite, making it highly efficient.

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?

The tool is relatively simple, and the description captures its core purpose and prerequisites. However, the optional reason and guild_id parameters are entirely unaddressed, and the description does not mention the existence of an output schema. Given the 0% schema description coverage, this is a notable gap.

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% and the description does not explain parameters like reason or guild_id. While it implicitly references user_id and role_id via 'server member' and 'role', it lacks explicit parameter guidance, leaving agents to infer from parameter names alone.

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 server member.' It specifies the resource (server member) and the operation (remove role), distinguishing it from sibling tools like assign_role and delete_role.

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 clear context for usage by stating prerequisites: 'Requires Manage Roles permission and bot role higher than target role.' This tells agents when the tool can be used but does not explicitly mention alternatives or exclusions.

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