remove_domain

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses that the route disappears on the next reconcile tick and that the operation is idempotent, but it omits auth requirements, whether the domain binding is permanently destroyed, and any effects on certificates or DNS.

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 compact clauses, with the core action stated first and the timing/idempotency caveats appended. Every phrase earns its place.

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 mutation tool with no annotations, the description gives important timing and idempotency context, and the schema is fully described. However, it leaves gaps around authorization, permanence, and edge-case behavior that an agent might need before invoking it.

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%, so the parameters are already well documented. The description reinforces domain removal but does not add syntax, format, or parameter-level meaning beyond what the schema provides.

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: 'Remove a custom domain'. It is clearly distinguishable from the sibling 'add_domain' and from service removal tools like 'remove_service'.

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 a deletion use case but does not explicitly state when to use this versus alternatives such as 'unshare_service' or 'remove_ai_route'. The schema carries most of the relevant conditions, including that removal is a no-op when nothing is bound.

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