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

Annotations already flag destructiveHint=true and openWorldHint=false, so the safety profile is partly covered; the description adds real context on top: publication is immediate, the live page lands on the custom domain only if the site is verified, and it names the two URLs the call yields. It still does not warn that the current live version is overwritten or that expectedVersion guards against clobbering concurrent edits.

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 sentences, verb-first, with no filler; the post-publication instructions are compact and action-oriented. Slightly dense embedding of three obligations (two URLs plus show_preview) in one sentence, but nothing is wasted.

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 destructive, no-output-schema mutation with two undocumented parameters, the description does well by naming the returned URLs and the required follow-up. It falls short on the expectedVersion semantics and on any explicit statement of what gets overwritten, which are the two things an agent most needs before firing a destructive publish.

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%, so the description carries the full burden for two required parameters. It alludes to "la version de brouillon indiquée" but never explains that expectedVersion is an optimistic-concurrency token (nor where to obtain it), and pageId is left entirely undefined; an agent cannot tell what happens if the version is stale.

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?

"Publier la version de brouillon indiquée immédiatement, sans redéploiement" names a specific verb (publish) and resource (the specified draft version) and adds the key qualifier that it takes effect immediately with no redeploy. It does not explicitly contrast with near-siblings such as publish_site_project, publish_template or edit_live_page, so the differentiation is only implied.

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?

The description prescribes a mandatory follow-up workflow (always surface publicUrl and editorUrl as clickable links, then call show_preview), which is genuinely useful sequencing guidance. However, it never states when to choose this over publish_site_project / rebuild_static_publication / edit_live_page, nor any precondition such as needing a draft version or a verified domain beyond the parenthetical.

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