hcloud_list_security_groupsLists security groups in a specified Huawei Cloud region, returning group details with an optional limit on results. Use it to inspect available groups before configuring network access rules.
List security groups
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results | |
| region | Yes | Region |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare read-only, open-world, and idempotent behavior. The description adds no further behavioral context such as region scoping, pagination, or what the listing returns, so it contributes little beyond the structured metadata.
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 two words, front-loaded, and free of filler. For a simple list operation, it is appropriately sized and easy to parse.
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?
The tool is simple and the schema plus annotations provide basic context, but the description omits scope, pagination, and return-shape hints despite having no output schema. It is minimally adequate rather than fully complete.
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 100%, so both the required region and optional limit parameters are documented by the schema. The description adds no additional meaning about parameter usage or constraints, making the baseline score appropriate.
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: "List security groups." This clearly identifies a collection-listing operation, but it does not explicitly differentiate itself from sibling tools such as hcloud_show_security_group or hcloud_list_security_group_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?
Provides no when-to-use guidance, prerequisites, or alternatives. The agent can infer that this tool lists security groups, but the description does not say when to choose it over hcloud_show_security_group or hcloud_list_security_group_rules.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.