List Load Balance Rules

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

Annotations already declare readOnlyHint=true, so the description is not required to carry the safety profile. However, it adds nothing beyond that: it does not say whether results are paginated, sorted, or whether an empty list means 'no rules configured' versus 'feature unsupported'. With annotations present the bar is lower, but this adds 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?

A single short phrase, fully front-loaded with the verb and resource, with no wasted words. It is terse to the point of thinness, but nothing is padded or buried.

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?

With an output schema present and no parameters, the description need not explain return values, so the essentials are covered. It nonetheless leaves the concept of '多线负载规则' (which rules, from which lines, whether disabled rules are included) undefined, which is a modest gap for a domain-specific listing tool.

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 the baseline of 4 applies: there is nothing for the description to clarify beyond what the (empty) schema already conveys.

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?

States a specific verb and resource ('列出' + '多线负载规则'), so an agent immediately knows it retrieves multi-WAN load-balancing rules. Among the siblings there is no other load-balance rule tool, so no differentiation is required, but the description does not clarify scope (all rules vs. active rules).

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 when-to-use guidance, no mention of prerequisites, and no pointer to a related alternative. The agent must infer usage purely from the name, which is acceptable only because the tool is a simple zero-parameter list.

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