domain_delete

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

Without any annotations, the description must disclose behavioral traits. It only says 'Delete', which implies destructiveness, but does not mention whether deletion is permanent, whether confirmation is needed, or any side effects like cascading removal of associated data. This is insufficient for a destructive operation.

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, which is extremely concise but under-informative. It lacks structure such as bullet points or front-loading of critical information (e.g., that the operation is irreversible). Conciseness is achieved at the expense of completeness.

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?

The tool is a destructive single-parameter operation but lacks crucial context: return value (despite having an output schema), error conditions (e.g., domain not found), or confirmation steps. The description is not complete enough given the tool's simplicity and the presence of an output schema that is not explained.

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 input schema has 0% description coverage, meaning the description does not elaborate on the 'domain' parameter. The description merely restates what the schema already shows. It adds no additional meaning, such as format expectations or examples, leaving the agent to guess the exact domain identifier required.

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 (Delete) and resource (SIP domain), and it effectively distinguishes from sibling tools like 'domain_add' and 'domain_list', which are for creating and listing domains respectively.

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 no guidance on when to use this tool, no prerequisites (e.g., domain must exist), and no conditions under which deletion should be avoided. Absent any usage context, an AI agent must infer from name alone.

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