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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risky profile is known. The description adds meaningful context beyond that: it defines what publish actually does (bakes draft + CMS state into deployed code) and that it requires a connected external host. It stops short of covering failure modes, latency, or revert behavior, so not a 5.

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 tight sentences: the core action first, then the gating constraint and where to verify it. Every clause earns its place with no redundancy.

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?

No output schema exists, and the description adequately covers what the tool does and the precondition for calling it. It omits what the response returns and what a failed/partial publish looks like, which matters for an open-world destructive action, so it is strong but not exhaustive.

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?

There is one parameter, siteId, and schema description coverage is 0%, so the description must carry the burden — but it never mentions siteId, its format, or where to obtain it. Implicitly 'the site' refers to it, but no concrete detail is added.

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 names a specific verb (publish) plus the resources acted on (every draft edit and CMS change baked into code) and the target (the user's connected Vercel/Netlify host). This clearly separates it from the design/edit siblings and from get_site/list_sites.

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 states an explicit precondition — 'Only works once a deploy target is connected' — and routes the agent to the exact check ('canPublish on get_site'). That is actionable when-to-use guidance with the gating condition spelled out rather than left to inference.

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