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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the internal pipeline (builds, packages, uploads, deploys), signaling a heavy multi-stage operation. It still omits whether the deploy is asynchronous, how failures surface, or what state is left behind on a partial failure.

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, effect stated first, prerequisite second, mechanism last. No filler and nothing buried.

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 description still tells the agent the required input source and the overall effect. It is nearly complete for a publish operation, lacking only failure/timeout behavior, which matters given the multi-stage build-and-deploy it describes.

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 100%, so both parameters are already documented in detail — including promoteRoutes' publish/draft semantics. The description's 'Requires the siteId from list_sites' merely repeats the schema's own note and says nothing about promoteRoutes. Baseline 3 applies.

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?

States a specific verb and resource (publish a site) and clarifies the effect — 'make changes live' — which separates it from draft-editing siblings like update_site and from create_shared_preview. It does not explicitly name an alternative sibling, 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?

It gives a prerequisite ('Requires the siteId from list_sites'), which is genuinely useful routing, but never states when to prefer this over alternatives such as update_site (draft edits) or create_shared_preview (non-live preview). Usage is implied by 'make changes live' rather than argued.

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