delete_host_mapping

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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful trait beyond the name: the deletion is applied immediately with no second confirmation, warning the agent that the action is irreversible. It omits other behavioral facts an agent needs, such as whether deleting a non-existent UUID errors, permission requirements, or idempotency.

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 short sentences, front-loaded with the action and resource, with the side-effect warning immediately after. No filler, though the second sentence could have carried more than the single immediacy fact.

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 complete schema documentation and no output schema, the description covers the action, the identifier, and the key side effect. The remaining gap is that no annotations exist to cover the safety profile, so more behavioral detail would have been welcome.

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 description coverage is 100% and the single parameter ('id', Host mapping UUID) is fully documented in the schema. The description echoes 'by UUID', adding no format, constraint, or sourcing information beyond what the schema already provides, so the baseline of 3 applies.

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 ('Deletes a native DNS custom Host mapping') plus the identifier type ('by UUID'), which distinguishes it from list_host_mappings and upsert_host_mapping in the sibling set. It stops short of naming those siblings or the relationship between them, so it is clear but not fully differentiated.

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?

There is no guidance on when to use this tool versus the sibling upsert_host_mapping or list_host_mappings, nor any prerequisite such as looking up the UUID first. Usage is only implied by the verb 'Deletes'.

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