Delete Hosting

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, consistent with 'deprovision'. The description adds genuinely new behavioral context beyond them: teardown is asynchronous ('scheduled by Porkbun') and irreversible in cost terms (re-provisioning is charged, no second free trial).

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?

Front-loaded with the action and resource, then a short parenthetical and one 'Note:' clause. Every clause carries information, though the sentence is slightly dense and could be split for clarity.

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 single-param destructive mutation with no output schema, the description covers the safety-relevant facts an agent needs: what is destroyed, that teardown is deferred, and that re-provisioning incurs cost. It lacks only explicit when-to-use/alternative routing.

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?

Only one parameter, and schema coverage is 100%, so the schema fully documents 'domain' (minLength 3, target of deprovisioning). The description adds no format, constraint, or meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 plus resource ('Deprovision (cancel) Secure Static Hosting') and scopes it to a domain, which distinguishes it from siblings like delete_hosting_file or create_hosting. 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?

The description implies usage (cancelling hosting) but never states when to use this versus alternatives such as delete_hosting_file or create_hosting, nor prerequisites like ownership of the domain. The free-trial note gives consequence context but not selection guidance.

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