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

The description adds significant behavioral context beyond the annotations: enabled:false makes the link 'not available' for everyone, makes /lp answer 404 inside the marketing chrome, suspends custom domains, and does not delete the site; enabled:true republishes it. This aligns with destructiveHint=false and idempotentHint=true, with no contradiction.

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?

The description is compact and front-loaded with user-facing trigger phrasing. There is slight redundancy between 'Use when...' and 'Takes a site offline or brings it back,' but each sentence contributes either behavioral detail or routing guidance, so it remains efficient.

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 simple boolean state-changing tool with no output schema, the description covers the essential outcome, side effects, non-destruction, and the fact that this is the only unpublish path. The workspace_id nuance is already fully covered by the schema, and a return-value description is not necessary for correct invocation.

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 the baseline is 3. The description adds operational meaning to the enabled parameter by detailing what false and true actually do, including the non-deletion and domain-suspension effects. It does not add to site_id or workspace_id, but the schema already documents those adequately.

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 states a clear action and resource: 'take it down, unpublish it, pause the link, or bring it back' and 'Takes a site offline or brings it back.' It also distinguishes itself from siblings by asserting it is the single way to take a site offline and that no separate unpublish tool exists, so an agent can route to it without ambiguity.

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 explicitly specifies when to use the tool ('Use when the user wants to take it down...') and provides an exclusion ('This is the single way to take a site offline; there is no separate unpublish tool'). It does not compare directly with publish_site, but the main alternative confusion is resolved.

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