Delete Domain

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the confirmation safety requirement that confirm_domain_name must match exactly, which is useful behavioral context beyond the annotations. It still does not explain downstream impact on fields that use the domain or whether the operation can be undone.

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 front-loaded sentence that states the action first, then the two invocation requirements. It is concise and wastes no words.

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 output schema exists, so return values need not be described, and annotations cover the destructive and idempotent profile. The description still leaves workspace_path undocumented and does not clarify the destructive switch beyond the annotation, making it only minimally complete for safe invocation.

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 description coverage is 0%, so the description must compensate. It only adds meaning for confirm_domain_name via the exact-match requirement; workspace_path is not explained, and domain_name is left to its self-evident title. Partial coverage of one of three parameters is insufficient at 0% schema coverage.

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 verb and resource — '删除指定属性域' — and clearly differentiates from sibling domain tools such as create_domain, alter_domain, and list_domains. An agent can identify this as the domain-deletion operation without opening the schema.

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?

It provides a clear precondition for invocation: a destructive switch is required and confirm_domain_name must match exactly. However, it does not name alternatives or explain when to prefer deletion over other domain operations such as alter_domain.

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