delete_domain_forwarding_rule

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'delete' without mentioning irreversibility, side effects, or whether the rule must exist. This is minimal disclosure that adds no value 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 extremely short, but this is under-specification rather than effective conciseness. It merely restates the tool name in Chinese and fails to provide any additional useful information.

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?

This is a simple tool with one parameter and an output schema, but the description is too sparse. It lacks operational context such as the need to list rules first, any prerequisites, or how deletion affects routing. The missing annotations and minimal description leave significant gaps.

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 one required parameter rule_id with zero description coverage. The description does not explain how to obtain rule_id or its meaning beyond the parameter name itself. The agent would have to infer from context that rule_id comes from listing domain forwarding rules.

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 indicates a delete operation on domain forwarding rules. The verb and resource are specific, and the action distinguishes it from list/add siblings. However, it lacks any additional scope detail that would earn a top score.

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, prerequisites, or alternatives. Related tools like list_domain_forwarding_rules and add_domain_forwarding_rule are not mentioned, leaving the agent without context on how this tool fits into the workflow.

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