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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description usefully adds what comes back (theme and preview document) and the post-read workflow, but says nothing about missing-component behavior, size of preview payloads, or errors.

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?

Two short sentences with zero filler, front-loading what is read and then what to do with the result. The intent of each clause is clear despite the non-English phrasing.

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 one-parameter read tool with no output schema, the description does state the return contents (theme, preview document) and the follow-up action, which is adequate. However, it leaves the componentId's provenance and format unexplained, which is the main thing an agent needs before calling.

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% and the single parameter componentId has no documented format, origin, or example. The description only mentions 'componentId' as an alternative to customizing, without explaining where such an id comes from (presumably search_components), so the coverage gap is not compensated.

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 specific verb ('Lire') and a specific resource set (a gallery section/native element, its theme, and its preview document). The agent can tell this is a fetch-a-component tool, though it never explicitly names the sibling it is not (e.g. search_components or preview_components).

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?

It gives concrete downstream guidance: customize the returned section/element before passing it to compose_page, or use its componentId directly. That routes the agent into a real workflow, but there are no stated exclusions about when to prefer search_components or preview_components instead.

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