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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description adds useful pipeline context (build, package, upload, deploy) that explains why the call is heavy and slow. It never spells out the actual risk implied by the destructive flag — that drafts become publicly visible and the change is not trivially reversible — nor whether the call is async or how long a deploy takes.

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 short sentences, front-loaded with the purpose, then the prerequisite, then the mechanics. No waste; the trailing fragment efficiently conveys the multi-stage deploy.

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?

There is no output schema, and the description says nothing about what a successful publish returns (a job id, a URL, a status) or whether the agent must poll for completion. For a destructive, non-idempotent deploy operation, that leaves a real gap, though the parameter documentation compensates on the input side.

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 coverage is 100% and both parameters are documented in detail, including the omit-vs-empty-array semantics of promoteRoutes. The description only repeats the siteId sourcing already stated in the schema, adding no meaning beyond it; baseline 3 applies when the schema does the heavy lifting.

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?

"Publish a site to make changes live" names a specific verb and resource, and the follow-up fragment clarifies that publishing is a build/deploy pipeline rather than a settings edit. It does not explicitly name a sibling to distinguish from (e.g. update_site, create_shared_preview), so it stops short of full differentiation.

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 gives one concrete prerequisite: the siteId comes from list_sites. There is no statement of when to publish versus alternatives such as create_shared_preview or update_site, and no guidance on exclusions or timing (e.g. publish after editing pages).

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