hcloud_list_sms_tasksLists SMS migration tasks in Huawei Cloud, with filters by name, state, and pagination to help track and manage server migrations.
List SMS (Server Migration Service) migration tasks
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Filter by task name | |
| limit | No | Max number of results | |
| state | No | Filter by task state | |
| offset | No | Offset for pagination | |
| 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, idempotentHint, and openWorldHint, but the description adds no further behavioral context such as ordering, default page size, region scoping, or behavior when a region has no tasks. For a paginated list tool, this leaves the agent with only the schema and annotations.
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 front-loaded sentence with no filler, and every word maps directly to the tool's purpose. It is terse, but terseness is assessed under other dimensions rather than as verbosity here.
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 description is minimal but the schema fully documents parameters and annotations cover the safety profile. It omits return ordering, pagination defaults, and the relationship to hcloud_show_sms_task, which are modest but real gaps for a five-parameter list 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?
Schema description coverage is 100%, so all five parameters are documented in the input schema. The description adds no additional meaning about required region scope, accepted state values, or pagination semantics, so the baseline of 3 applies.
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 ('List') and resource ('SMS (Server Migration Service) migration tasks'), and expands the SMS acronym. It implicitly distinguishes from hcloud_show_sms_task and from sibling list tools for servers or migration projects by resource, but does not explicitly name any sibling.
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, no mention of when to prefer hcloud_show_sms_task for a single task, and no advice on combining filters. The only usage cue is the verb 'List' in the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.