List Domain Forwarding Rules

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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally, but the description adds nothing beyond that — no mention of result scope, ordering, pagination, or whether the read is cheap. It contributes zero behavioral context.

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?

It is short, but that shortness is under-specification rather than conciseness — the single phrase duplicates the title instead of earning its place. Structurally there is nothing front-loaded because there is no real content.

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?

An output schema exists so return values need not be explained, and the tool is a simple parameterless read. Still, with many similarly named 'list_*_forwarding_rules' siblings, the description should at minimum disambiguate domain forwarding from port/protocol forwarding; it does not.

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 tool takes zero parameters, so there is nothing for the description to clarify; the baseline for a parameterless schema is 4. The description neither helps nor hurts here.

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 '列出域名分流规则' simply restates the tool name and title in another language, adding no scope, verb nuance, or distinguishing detail. It is a tautology rather than an explanation of what the rules are or what listing them returns.

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?

No guidance on when to use this tool, no prerequisites, and no mention of the closely related siblings add_domain_forwarding_rule / delete_domain_forwarding_rule, nor of how it differs from list_protocol_forwarding_rules or list_port_forwarding_rules. The agent must infer usage entirely.

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