delete_domain

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

With no annotations provided, the description carries the full behavioral burden. It explicitly warns 'This cannot be undone,' which is critical for a destructive operation, and explains the auth access model via PROOF_API_KEY or start_login. It does not detail side effects on associated resources, but the key hazards are covered.

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?

The description is compact and front-loaded: purpose first, irreversibility warning second, and access instructions last. Every sentence earns its place with no filler.

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 provides enough to invoke safely: what it does, that it is irreversible, and how to authenticate. It omits minor conveniences like how to obtain the domain ID, but nothing essential is missing.

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?

The schema already covers the only parameter 'id' with the description 'Domain ID to delete', and coverage is 100%. The description adds no further parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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?

The first sentence states a specific verb ('remove'), resource ('domain'), and scope ('from the account'), making the tool's function immediately clear. It also distinguishes itself from domain-related siblings like add_domain, verify_domain, and get_domain.

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 to use the tool — when a domain should be permanently removed — and clearly states authentication prerequisites. However, it does not explicitly mention alternatives or when not to use this tool, so some guidance is left to inference.

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