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

Annotations already cover the read-only, non-destructive, closed-world profile, so the bar is lower. The description still adds real behavior: the review is compact and persistent, it contains stale checks/anomalies/next action, and pagination must follow issuePagination.hasMore rather than silently truncating anomalies — a return-field detail the annotations cannot supply.

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 sentences, front-loaded with the purpose, and no filler. The closing line 'Ne pas demander de continuer' is cryptic out of context and the middle sentence packs pagination rules densely enough that it reads as shorthand rather than instruction.

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 3-parameter tool with no output schema, the description usefully sketches the payload (checks, anomalies, next action) and pagination behavior. The required pageId is left unexplained in both schema and description, so an agent knows more about the response than about the mandatory input.

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% for 3 parameters, so the description must carry the load. It meaningfully explains issueOffset/issueLimit (paging governed by issuePagination.hasMore, no silent truncation) but says nothing about pageId, which is the required parameter and the one whose semantics are least obvious.

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?

States a specific verb ('Lire') and resource ('suivi compact et persistant des corrections du clone'), then enumerates what the record holds: stale checks, anomalies, next action. That is enough to separate it from write-side siblings like record_clone_review and apply_clone_repairs, though the sibling names are never referenced and the wording is French against English tool names.

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?

Gives one concrete usage moment ('Lire au démarrage/reprise') and one caution ('Ne pas demander de continuer'), which is more than most definitions. It never names the alternative tool for writing review state (record_clone_review) or explains when not to call this one, so the routing guidance is implied rather than explicit.

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