supprimer_role

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

No annotations exist, so the description carries the full behavioral burden. It hints at a side effect on member assignments ("ne sont pas sauvegardées automatiquement") but this phrasing is ambiguous — it is unclear whether assignments are deleted, orphaned, or left untouched, and nothing is said about irreversibility or required authorization.

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?

Three short sentences with no padding, but the front-loaded "APERÇU" is the least informative and most confusing element to lead with. Restructuring around the delete action and its consequence would earn the space better.

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 destructive mutation with no annotations, no output schema, and an undocumented required parameter, the description should state permissions, irreversibility, and what happens to member assignments. The current text leaves all of these unresolved.

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% and the single parameter role_id has no description in the schema. The description adds no meaning about what role_id is, its expected format, or how to obtain it, so the one required parameter is effectively undocumented.

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?

"Supprimer un rôle" is a clear verb+resource, but the leading token "APERÇU" (preview) directly muddies whether this actually deletes the role or only simulates it. The agent cannot tell the operation mode apart from the sibling modifier_role/creer_role without guessing.

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 statement of when to use this versus modifier_role (edit) or role_membre (unassign members), and no prerequisite such as permissions or hierarchy checks. The only guidance is an implicit warning about member assignments.

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