list_protocol_forwarding_rules

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

The readOnlyHint annotation already indicates a safe read operation, but the description adds no additional behavioral context. It does not state that all protocol forwarding rules are returned, whether any filtering or pagination applies, or what the output contains. Beyond the annotation, the description provides zero transparency.

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 directly states the tool's function. It is appropriately concise for a zero-parameter read-only list operation, with no filler or redundant 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?

Given the tool's simplicity (no parameters, read-only, output schema exists), the description is minimally adequate. However, it does not clarify the exact scope of 'protocol diversion rules' or distinguish them from closely related forwarding rule types, leaving some ambiguity in a crowded sibling context. The presence of an output schema partially compensates for missing return-value details.

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 has zero parameters, so the schema fully covers all inputs (vacuously). Baseline for 0 params is 4; the description does not need to explain any parameter details. No additional parameter semantics are 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 (list) and the resource (protocol diversion/forwarding rules), making the tool's purpose obvious. It distinguishes from sibling tools that list port or domain forwarding rules by specifying 'protocol', though it does not explicitly contrast with those alternatives.

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 usage guidance is provided. The description does not indicate when to use this tool over the many sibling list tools (e.g., list_app_protocol_rules, list_port_forwarding_rules), nor does it mention any prerequisites or intended scenarios.

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