delete_domain

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

With no annotations, the description carries the full burden of explaining behavior. It indicates that a domain is removed, but it does not disclose whether removal is irreversible, what happens to associated records, aliases, or email hosting, or whether permissions are required. For a destructive operation, this is a significant transparency gap.

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 one short sentence with no redundant words. It communicates the primary purpose immediately and front-loads the core action, so it is highly concise and well-structured for its length.

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 domain deletion tool with zero annotations and no parameter descriptions, the description is too sparse. It omits critical context such as whether deletion is reversible, whether primary domains can be deleted, and what effects occur on related domain features. An agent cannot fully assess the operation's impact from the available information.

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 has no parameter descriptions, and the description only vaguely implies that 'domain' maps to domain_name and 'organization' relates to zoid. It does not explain what zoid is, what format domain_name should take, or how the two parameters relate to the operation.

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 states a specific action ('Remove') and a resource ('domain from organization'), which makes the core purpose understandable. It is mostly clear but does not specify what kind of domain or what removal entails, so it stops short of being fully self-contained.

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 gives no guidance on when to use this tool versus alternatives like remove_domain_alias or delete_domain_alias. There is no mention of prerequisites, restrictions, or when not to use it, so an agent must infer usage from context alone.

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