list_connection_limits

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds no behavioral traits beyond the tool's purpose—no mention of pagination, scope, or output behavior. It is essentially a restatement of the tool name and contributes nothing beyond the annotation.

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 sentence, which is concise and front-loaded. However, it merely restates the tool name in Chinese, adding no new information. It is not bloated but also does not earn its place substantively, making it average for conciseness.

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 read-only listing tool with no parameters and an output schema, the description is minimally viable. It tells the agent it lists connection limits but lacks additional context about the scope (e.g., all rules), possible interactions with other tools, or edge cases. The presence of an output schema mitigates some gaps, but the description alone is thin.

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 baseline for parameter semantics is 4. The description does not need to explain parameters, and the lack of filters in the description implies the tool lists all connection limits without any input constraints.

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 tool lists connection limit rules ('列出连接数限制规则'), using a specific verb ('list') and a specific resource ('connection limit rules'). It distinguishes from sibling tools like add_connection_limit and delete_connection_limit by the listing action.

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 versus alternatives. It does not mention any exclusions, prerequisites, or reference to sibling add/delete tools, leaving the agent without usage context.

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