hcloud_list_smn_topicsLists SMN (Simple Message Notification) topics in a specified Huawei Cloud region, with optional limit and offset parameters to paginate results.
List SMN (Simple Message Notification) topics
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results | |
| offset | No | Pagination offset | |
| region | Yes | Region |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered structurally. The description adds no behavioral context beyond the tool name, such as pagination behavior, region requirements, or what the returned topic entries include.
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 with no redundant or filler wording. It is appropriately concise for a simple list tool.
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 low-complexity list tool with annotations and full schema coverage, the description covers the core purpose. However, it leaves out practical context such as pagination behavior and how it relates to hcloud_list_smn_subscriptions, which would help an agent call it with confidence.
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 all three parameters—limit, offset, and region—are already documented in the schema. The description adds no extra parameter semantics, but the baseline is 3 because the schema carries the parameter documentation.
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 states a specific verb ('List') and resource ('SMN topics') and expands the acronym, so the agent knows what is returned at a high level. It does not distinguish this tool from nearby siblings such as hcloud_list_smn_subscriptions, but the resource name is specific enough to avoid ambiguity.
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 gives no guidance on when to use this tool versus related list tools, nor any prerequisites, exclusions, or expected context such as region scoping. The intended use as a simple list operation is implied by the name, but no explicit when-to-use guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.