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

With destructiveHint already set, the description still adds substantial context: atomic replacement of the site's files, retryability because the upload stays open on failure, and the draft fallback plus published=false when the monthly allowance is exhausted. This is exactly the kind of consequence and edge-case disclosure annotations cannot carry.

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 sentences, front-loaded with the core action and its destructive effect, then failure semantics, then the quota edge case. The rule enumeration ('root index.html, website files only, plan limits, content checks') is dense but earns its place as precondition guidance.

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, non-idempotent publish with no output schema, the description covers what gets replaced, what happens on failure, and how the caller learns the outcome (published=false). Only the provenance of uploadId is left out, a minor gap against the rest.

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 single uploadId parameter has 0% schema description coverage, so the description must compensate. It implies uploadId identifies an upload holding files, but never says where that id comes from (start_upload) or that the upload must still be open – so the one ambiguous parameter stays partially ambiguous.

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 with scope: 'publishes every file an upload holds as one atomic deploy,' including that it replaces the site's files or creates the site. It's clearly distinguishable from start_upload/upload_files, but never names deploy_site to route the agent between the two publishing paths.

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?

Usage is only implied by 'every file an upload holds' – an agent can infer it comes after start_upload/upload_files – but there is no explicit when-to-use or when-not versus deploy_site. The failure and rate-limit behaviors are covered, which is more about outcome than selection.

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