delete_website

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not the destructive/irreversible nature, not whether associated files, databases, or SSL certificates are removed, not permission requirements, and not whether the action can be undone or recovered from the recycle bin.

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 words are not conciseness here but under-specification; there is nothing to be front-loaded because no substantive content exists.

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?

A destructive, unannotated mutation tool with an undocumented ID parameter and no output schema still leaves the description completely inadequate — an agent cannot safely invoke this tool on the basis of the provided information.

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 required parameter 'id' has 0% schema description coverage (bare number type), and the description adds no meaning — it does not say whether this is a website ID or domain ID, nor where the agent should obtain a valid value.

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?

"Delete website" merely restates the tool name with no additional specificity — no indication of scope (does it remove the domain binding, files, database, SSL cert, nginx config?). It also does not distinguish itself from siblings such as update_website or uninstall_app, which could plausibly be confused with it.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives or consequences. An agent gets no signal about when deletion is appropriate versus when update_website or another destructive sibling should be used instead.

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