remove_domain

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

Despite no annotations, the description warns of permanence and traffic stoppage, and mandates a specific confirmation. It does not detail side effects on related resources, but is clear for a destructive action.

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 a single sentence with an emoji warning, extremely concise and front-loaded with the most critical information (permanence, effect, confirmation).

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 destructive tool with no output schema and no annotations, the description covers purpose, consequence, and confirmation requirement. It could mention how to obtain domainId (though schema references list_domains), but is reasonably complete.

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% with per-parameter descriptions; the tool description adds overall context but only marginally improves parameter understanding beyond the schema's own explanations.

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 description clearly states the action is to permanently remove a domain, with explicit consequence ('traffic will stop'), and distinguishes from siblings like add_domain and list_domains.

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 provides clear context (usable when permanent removal is needed) and specifies the required confirmation string, though it does not explicitly list when not to use or suggest alternatives.

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