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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds almost no behavioral context: it does not say whether the result is a static reference document, a live introspection of the current page, or what 'vérifications visuelles' actually entails.

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?

It is a single short sentence, but it is densely packed with undefined jargon and semicolon-separated fragments ('types exacts, fusion des mises à jour'), and it is not front-loaded with a statement of what the tool returns. Brevity here comes from under-specification rather than economy.

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 and no parameters, the description is the only source of information about the return value, and it fails to describe it — an agent cannot tell what shape or content the capability report takes. It also does not disambiguate from the numerous other describe_* tools.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to carry. Baseline 4 applies; nothing is missing on this dimension.

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 is a noun phrase listing editor features ('animations, survols, mosaïque responsive, lectures ciblées') rather than stating what the tool does. Only the name/title ('describe_editor_capabilities') tells an agent this is a read-only documentation lookup; the description itself never uses a verb or says it returns capability information, and it is written in French while the sibling tool set is English.

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 guidance, no preconditions, and no mention of any alternative, despite many closely related siblings (describe_page_composition, describe_page_style, get_operator_guide, describe_automation). An agent has no basis for choosing this tool over those.

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