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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful nuance beyond them: the site persists as a draft, is republishable, and custom domains stop pointing at it until then — clarifying that 'destructive' here does not mean data loss. It does not mention auth requirements or whether the domain change is immediate/instant.

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 with no filler, and the triggering condition plus the side effects are stated up front. Leading with 'Use this when' rather than the action verb is the only minor structural weakness.

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 an output schema present, return values need not be explained, and the annotations carry the safety profile. The description covers intent and post-conditions well; the only real gap is the undocumented site_id parameter.

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 0% and the description never mentions site_id or how the target site is identified. Although a single site_id is largely self-evident, the parameter is undocumented in both structured fields and prose, so the description does not compensate for the coverage gap.

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 ('take their published WebTwizz site offline'), which is clearly distinct from siblings like delete-site-data, publish-site, and update-site. An agent can identify the operation without opening the schema.

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?

'Use this when the user wants to take their published site offline' gives a clear triggering intent. It stops short of naming the adjacent alternative (e.g., versus delete-site-data or edit-site) or stating exclusions, so it is context without explicit routing.

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