Add Domain Forwarding Rule

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. For a mutation tool it does not state whether the rule takes effect immediately, what permissions are required, what happens on conflict with an existing rule, or whether the change is reversible.

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 short phrase with no wasted words, but that brevity reflects under-specification rather than conciseness. It is not front-loaded with any actionable detail because there is none.

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 5-parameter write operation with zero annotation coverage and no schema descriptions, this description is wholly inadequate. The presence of an output schema does not compensate, since the agent still cannot determine how to invoke the tool correctly.

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% across 5 parameters, and the description provides no parameter information at all. Fields like src_addr, interface (defaulting to 'wan2'), and enabled have non-obvious semantics that are left completely undocumented.

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 "添加域名分流规则" is a direct translation of the tool title 'Add Domain Forwarding Rule' and adds no information beyond the name. It states a verb and resource, but is effectively a tautological restatement with no scope or differentiation from siblings like add_port_forwarding_rule or add_acl_rule.

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?

There is no guidance on when to use this tool versus the many sibling rule-creation tools (add_port_forwarding_rule, add_static_route, add_acl_rule, etc.), nor any mention of prerequisites or the existence of list_domain_forwarding_rules / delete_domain_forwarding_rule. Usage must be entirely inferred from the name.

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