Delete Hosting

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

Annotations already flag destructive/idempotent, but the description adds genuinely new behavior: teardown is scheduled by Porkbun rather than instantaneous, a paid Link in Bio page survives by downgrading to the free plan with content preserved, and the free-trial is consumed so re-provisioning incurs a charge. These are consequences an agent cannot infer from structured fields.

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?

Three compact sentences, front-loaded with the action and timing, followed by side effects and then the alternative. No filler, and the negative-space detail (Link in Bio, trial consumed) earns its length.

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 one-parameter destructive tool with no output schema, the description covers timing, side effects, and the alternative. It stops short of saying what happens to hosted site files/content in the general case (only the Link in Bio exception is described), which is the one remaining unknown an agent might need.

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 coverage is 100% for the single required 'domain' parameter, so the schema already carries the meaning. The description adds no format, validation, or eligibility detail about the domain argument, making baseline 3 the correct floor.

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 and resource ('Deprovision (cancel) hosting on a domain') and immediately constrains the timing ('now'). It is clearly distinguishable from siblings like get_hosting and update_hosting_auto_renew, which it names directly.

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?

Explicitly gives the alternative path: 'To let a plan run to the end of its term instead, use update_hosting_auto_renew with auto_renew false.' This is precisely the decision an agent must make before cancelling hosting.

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