Détails d'un(e) rôle

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds only 'informations détaillées' (detailed information) and 'par son ID', which is minimal extra context. No contradictions with annotations, but no additional behavioral traits are disclosed.

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, clear sentence that is appropriately front-loaded with the verb and resource. It contains no unnecessary words or 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 get-by-ID tool, the description provides sufficient context to select and invoke it. It clearly states that it retrieves detailed information by ID. There is no output schema, but the description's 'informations détaillées' gives a general sense of the return value. It is not overly vague for the tool's simplicity.

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?

The input schema already provides a 100% coverage description for the single parameter 'id', including type, pattern, and a description of what it is. The tool description does not add further semantic detail beyond repeating that the tool uses an ID, so the baseline 3 applies.

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 'Récupère' (retrieves) and identifies the resource 'rôle' and method 'par son ID'. This clearly distinguishes it from sibling tools like boond_roles_search, which searches for roles.

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 clearly implies that the tool is used when you have a role ID and need detailed information. It does not explicitly mention alternatives or exclusions, but the context is evident from the 'par son ID' phrasing, which indicates it is not for searching without an ID.

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