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, destructiveHint=false, idempotentHint=true, covering safety and idempotency. The description adds context ('informations détaillées') implying a complete role object is returned. There is no contradiction. The description complements annotations well.

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 sentence, no wasted words. It is front-loaded with the action and resource, then the parameter. Perfectly concise.

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?

With a simple input schema (one required ID), annotations covering safety, and no output schema, the description is largely adequate. It could mention the return structure (e.g., 'returns the full role object'), but the tool's purpose is clear. Almost 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 coverage is 100% (one parameter documented with regex pattern and description). The description adds no additional meaning beyond 'par son ID', which mirrors the schema. Baseline score of 3 is appropriate.

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 ('Récupère les informations détaillées'), the resource ('rôle'), and the identifier method ('par son ID'). This verb+resource formulation distinguishes it from sibling tools like boond_roles_search (which searches/filters) and other getters.

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?

No explicit when-to-use or when-not-to-use guidance is provided. While it's clear this tool retrieves a single role by ID, there is no mention of alternatives like boond_roles_search for querying multiple roles or filtering. The context is adequate but could be improved.

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