delete_custom_hostname

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

Describes the confirm gate and preview functionality, adding value beyond annotations. Does not explicitly address idempotency hinted by annotations, but overall disclosure is strong.

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 sentences, front-loaded, no wasted words. Efficiently conveys the essential purpose and a critical usage condition.

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?

Adequately covers the key behavior and confirm gate given the simple delete operation. Lacks details on success/error output or idempotency, but not critical due to annotations and schema richness.

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?

Adds context for all three parameters: zone_id from list_zones, custom_hostname_id from list_custom_hostnames, and confirm behavior. Schema coverage is 100%, and description complements it well.

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?

Clearly states the action 'Delete a custom hostname by ID', using a specific verb and resource. Differentiates from other delete tools in the sibling list.

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 explains the confirm requirement and the preview behavior without confirm. Does not mention alternatives, but no direct alternative exists for this specific delete action.

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