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

Annotations flag destructiveHint=true and idempotentHint=false, but the description never explains what is destroyed (e.g., a previously published version is replaced) or that repeat calls produce different results. It also omits the rights_confirmed precondition, which the annotation profile alone cannot convey.

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?

It is a single front-loaded sentence with no filler, which is good structurally. However, the brevity is under-specification rather than earned concision given the destructive, multi-mode nature of the operation.

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 tool with four parameters and no output schema, the description should explain the two operating modes (publishing a draft preview vs. keeping a preview on a subdomain) and the consequences of publishing. None of that is present.

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 parameter meaning is already fully documented, including the draft_id-vs-site distinction and the subdomain case. The description adds no parameter semantics beyond the schema, which is the baseline expectation at full coverage.

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 gives a verb and resource ('put the current version of a site out for people to read'), which conveys roughly what publish means. But 'out for people to read' is a loose paraphrase that never says 'make publicly accessible' or 'replace the live version', and it does not distinguish this from siblings like create_preview or claim_draft.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as create_preview (which the schema references) or claim_draft. The agent must infer that create_preview must precede this call and that claim_draft is a different path.

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