remove_role

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

With no annotations supplied, the description carries the full behavioral burden and discloses almost nothing: it does not say whether the action requires elevated permissions, whether role hierarchy rules apply, what happens if the member lacks the role, or that a 'reason' is recorded to the audit log. It only conveys the bare mutation implied by the name.

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?

It is a single short sentence with no filler, so there is nothing to trim, but the brevity comes from under-specification rather than disciplined editing. A little more front-loaded detail would earn its place here.

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?

A destructive mutation with no annotations, no output schema, and zero parameter documentation needs far more than one sentence. The definition leaves the agent without the permission, hierarchy, failure-mode, or return-value context required to invoke it safely.

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% across four parameters (guild_id, user_id, role_id, reason), and the description adds no meaning for any of them — notably it never mentions that 'reason' exists or how it is used. An agent gets no semantic help beyond the bare property names.

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 states a specific verb and resource ('Remove um cargo de um membro' = remove a role from a member), which implicitly separates it from sibling delete_role (which destroys the role itself) and add_role. However, it never names those siblings explicitly, and it is written in Portuguese while the rest of the tool surface is English.

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?

There is no guidance on when to use this versus add_role, delete_role, or edit_role, and no mention of prerequisites such as needing Manage Roles permission or a role positioned below the bot's highest role. The agent must infer all usage conditions.

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