Récupère la liste des utilisateurs (vendeurs, gérants, etc.) rattachés à la boutique, avec leurs rôles et identifiants.

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

The annotations declare readOnlyHint=true, which the description doesn't contradict. However, the description adds no behavioral context beyond what annotations provide - no information about authentication needs, rate limits, pagination, or what specific user data is returned. With annotations covering the safety aspect, this gets a baseline score.

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?

While technically concise (only 4 words), the description is under-specified rather than efficiently concise. It contains grammatical errors ('Liste des Lister') and fails to communicate essential information, making it an example of harmful brevity rather than effective conciseness.

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 read-only listing tool with no output schema, the description should provide more context about what data is returned (users with roles and identifiers as mentioned in the title) and how results are structured. The current description is inadequate given the tool's purpose and the lack of output schema documentation.

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?

With 100% schema coverage (1 parameter with enum values clearly documented in the schema), the baseline is 3. The description adds no parameter information beyond what's already in the structured schema, which fully documents the 'format' parameter with its enum values and default.

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 'Liste des Lister les utilisateurs' is tautological - it essentially repeats the tool name 'data_list_users' with grammatical errors. The title provides better context ('Récupère la liste des utilisateurs...'), but the description itself fails to clearly state what the tool does beyond restating the name.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'data_list_clients' and 'data_list_delivery_men' that also list different entity types, there's no indication of when this user-listing tool is appropriate versus those other listing tools.

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