hcloud_list_oms_sync_tasksLists OMS object storage migration sync tasks by region, with optional limit and offset for pagination, to help monitor migration progress.
List OMS (Object Storage Migration Service) sync tasks
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max number of results | |
| 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?
The annotations already communicate that the operation is read-only, idempotent, and open-world. The description adds no behavioral context beyond those fields, such as result scope, pagination behavior, permissions, or whether tasks from all statuses are included.
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 single sentence is concise, front-loaded, and contains no unnecessary wording. Expanding the OMS acronym is a useful inclusion despite the brevity.
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 simple schema and safety annotations make the definition minimally sufficient for invocation. However, with no output schema, the lack of detail about returned task information and the ambiguous distinction from hcloud_list_oms_tasks leave noticeable gaps.
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 region, limit, and offset are already documented and the baseline score applies. The description adds no further meaning, such as region constraints, pagination defaults, or recommended limit values.
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 verb and resource: listing OMS sync tasks, and usefully expands OMS as Object Storage Migration Service. It does not explicitly clarify how these sync tasks differ from the tasks returned by sibling hcloud_list_oms_tasks.
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 explicit guidance on when to use this tool or which alternative to choose for other OMS task queries. In particular, it does not distinguish itself from hcloud_list_oms_tasks or direct agents to hcloud_show_oms_task for individual task details.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.