parse_remove_users_from_role

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

No annotations are provided, so the description carries the burden of disclosing behavior. It does state the main effect (users lose associated permissions) and the master key requirement, but it omits return value, error behavior, and reversibility, which are meaningful gaps for a mutating operation.

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 two concise sentences, front-loaded with the action, followed by effect and authentication requirement. Every sentence adds value and there is no unnecessary filler.

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?

For a simple mutation tool, the description covers the core operation, effect, and auth prerequisite. However, with no output schema or annotations, it leaves out response format, error cases, and whether the action is reversible, making it only minimally complete.

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% per the context signal, and the description only mentions 'objectIds' without clearly mapping to the roleId and userIds parameters. The nested schema does provide some descriptions, but the tool description itself fails to compensate for the low coverage.

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 uses a specific verb ('Remueve') and a clear resource ('usuarios de un rol'), and the effect ('perderán los permisos') makes the tool's function unambiguous. It is clearly distinct from sibling tools like parse_add_users_to_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 establishes when to use the tool (to remove users from a role) and states a key prerequisite (requires master key). It does not explicitly mention alternatives or when not to use it, but the purpose and sibling context make that obvious.

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