Delete Domain Pointer

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

Annotations already declare destructive=true, idempotent=true and readOnly=false, so safety is structured. The description still earns credit by spelling out the actual effect — the pointer domain stops serving the target's mailboxes while the target is unchanged — which is real blast-radius information annotations cannot convey. It stops short of stating whether the pointer record is recoverable or what happens if the pointer does not exist.

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, effect first and scope-reassurance second, with no filler. Every clause carries information an agent would otherwise have to guess.

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 two-parameter destructive delete with an output schema and full annotation coverage, the description supplies the key missing piece: what breaks and what does not. Minor gaps remain around error behavior for nonexistent pointers and whether the change is reversible, but nothing essential to calling it correctly is absent.

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%, but both parameters carry identical boilerplate ("Domain name on this account..."), leaving the domain/pointer roles ambiguous in the schema alone. The description resolves this by framing it as removing a pointer domain from a target domain, which is genuine added meaning. It still does not state the expected format or which direction the alias points.

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?

"Removes a domain pointer (alias or redirect) from a domain" names a specific verb and resource, and the parenthetical disambiguates what a pointer actually is. The follow-up clause separates this from delete_domain by stating the target domain is untouched, so the agent can distinguish it from siblings 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 when this applies (detaching a pointer/alias from a domain) but never states preconditions, alternatives, or exclusions. It does not point to create_domain_pointer or list_domain_pointers as the complementary or lookup operations, so routing must be inferred from sibling names.

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