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

Beyond the destructive and open-world annotations, the description explains exactly what is removed versus preserved: the EmDash Worker is removed but its database and login storage remain by default, while deleteData irreversibly destroys CMS content and users. It also discloses the publisher-only authorization constraint.

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 purpose is front-loaded in the first sentence, followed by mode-specific consequences and then the confirmation requirement. Despite being dense, every clause adds necessary operational or safety information.

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 deployment tool with no output schema, the description covers the key decision points: which site mode to choose, whether to delete data, who may invoke it, and the need to confirm. It does not describe expected return values or failure behavior, but the core calling guidance 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?

The description adds substantial meaning to the site enum by explaining the difference between emdash and static, and it explains the irreversible consequence of deleteData. The required projectId parameter is only implied by the phrase "project's site" rather than explicitly documented.

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 uses a specific verb and resource: taking a project's Cloudflare-hosted site OFFLINE. It clearly separates the EmDash site mode from the static deploy mode, so an agent knows exactly what operation this tool performs.

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 gives clear context for use, including the default EmDash mode, the deleteData escalation, the publisher-only permission rule, and the instruction to confirm with the user first. It references the inverse publish tool but does not explicitly compare this tool with siblings such as uichemy_unpublish_site.

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