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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only 'pagination et filtres', which merely restates the presence of `page`/`limit`/`filter` parameters already visible in the schema; it says nothing about default page size, maximum result caps, sort order, or what happens with an invalid `type`.

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?

A single compact sentence with no filler and the core concept front-loaded. It is efficient, though brevity here comes at the cost of substance rather than from disciplined editing.

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?

The tool has 8 undocumented parameters, a 50-value required enum, and no output schema, which is a lot of surface for one sentence. Because there is no output schema the description needn't explain return values, but it should at least explain how `type` drives which other parameters are valid and what the list envelope looks like (items vs. total).

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% across 8 parameters, so the description must compensate and does not. It gestures at pagination and filtering but never explains the meaning of `q` (free-text search?), `kind` (media type), `status`, `segmentId` scoping, or what the ~50 `type` enum values select, and the enum is a bare list with no labels.

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 states a verb pair (list and search) and a resource, but the resource is described only as 'les éléments d'un module', while the `type` enum actually spans ~50 distinct entity families (contacts, orders, pages, deals...). It gives no differentiation from siblings like get_record, batch_records, or the many entity-specific list_* tools, so an agent cannot tell from the text when this generic lister applies versus a dedicated one.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g., required `type` value), and no pointer to alternatives such as get_record for a single item or list_collection_rows for collection data. Usage is only implied by the word 'Lister'.

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