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 covered. The description adds the useful detail that the call surfaces runtime state (status, checkpoint, history) rather than just a static definition, but says nothing about permissions, failure modes for an unknown id, or result size.

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?

One front-loaded sentence with no filler, and the enumerated fields are a compact way to convey what comes back. It is slightly dense as a comma list rather than structured, and its French wording is inconsistent with the otherwise English tool surface.

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 no output schema, the field enumeration usefully substitutes for a return-value specification, and the annotations cover the safety profile, so an agent has enough to call it. The gaps are the missing not-found/error behavior and the absence of any pointer to how an id is obtained.

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 the single "id" parameter, so the description carries the burden. It weakly compensates by making clear the id designates a collection, but it does not state the format, where the id comes from, or the 1-64 character constraint already in the schema.

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 opens with a specific read verb ("Lire") applied to a named resource ("la collecte") and enumerates the facets returned: definition, version, per-source plan, status, checkpoint and history. That is far more specific than a restatement of the name, though it never contrasts itself with the near-sibling describe_collections or list_collections, so the agent must still infer the boundary.

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 guidance on when to call this versus describe_collections, list_collections, claim_collection or report_collection, and no stated prerequisite such as needing an id obtained from list_collections. Usage is only implied by the noun "la collecte".

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