domain_delete

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'delete' which implies destructiveness but provides no details on irreversibility, authorization, rate limits, or side effects. The description adds minimal behavioral context beyond the tool name.

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 highly concise, uses structured sections with emojis and bullet points for clarity, and front-loads the core action. Every sentence and symbol adds value without redundancy.

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 simple delete operation with one parameter and no output schema, the description covers the essentials: purpose, usage scenarios, alternatives, and prerequisites. It does not explain return values, but that is acceptable given the action's triviality.

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% and the schema already describes the 'id' parameter as 'ID of the domain to delete'. The description does not add any additional meaning or constraints beyond that baseline, so it merits a standard score of 3.

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 explicitly states 'Delete a domain from a service' and lists specific best use cases like removing unused domains and cleaning up configurations. It distinguishes from sibling tools by noting it is not for temporary disabling or port updates, which are covered by domain_update.

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 when-to-use and when-not-to-use guidelines, mentions prerequisites (domain_list), alternatives (domain_update), and related tools (service_update). This fully informs the agent about context and selection.

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