agency-hosting_deleteWebsiteV1

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

The description explicitly discloses the asynchronous deletion process: 'the website is immediately transitioned to a deleting state and the underlying server resources are removed in the background.' It also states the deletion is permanent, which is critical behavioral information. With no annotations, this fully covers the transparency burden.

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 concise, consisting of two clear sentences. It avoids redundancy and directly conveys the essential information without unnecessary fluff.

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?

Given the single parameter and no output schema, the description sufficiently covers the action, the asynchronous behavior, and the permanent nature of the deletion. It provides enough context for an agent to understand the operation's implications without missing critical details.

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 only parameter, website_uid, is described in the schema as 'Agency Plan website UID'. This is consistent with the tool's purpose. The description does not add further details beyond what the schema already provides, so it meets the baseline but lacks additional semantic clarity.

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 clearly states the function: 'Permanently deletes an Agency Plan website.' It is specific to Agency Plan websites, distinguishing it from other delete operations for different resource types. The asynchronous aspect is also noted, making the purpose unambiguous.

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?

The description implicitly indicates when to use this tool (for deleting Agency Plan websites) but does not explicitly compare with alternatives like hosting_deleteWebsiteV1. The resource type is clear, and the async behavior is mentioned, but there is no direct guidance on choosing this over other deletion tools.

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