hcloud_list_oms_tasks

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

The annotations already establish 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, or status-filtering semantics.

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 direct, front-loaded, and contains no unnecessary wording. Expanding the OMS acronym makes the terse description informative without adding clutter.

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 simple four-parameter read-only list operation with fully described inputs, the description is minimally adequate. It remains incomplete for confident selection because it does not differentiate OMS tasks from sync tasks, and it provides no additional result or filtering context despite the absence of an output schema.

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, offset, and status are already documented and the baseline score applies. The description adds no parameter guidance, such as valid status values or how limit and offset interact.

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 tasks—and usefully expands OMS as Object Storage Migration Service. It does not distinguish these tasks from the sibling sync-task listing or the single-task detail tool.

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?

An agent can infer that this tool is appropriate when it needs a collection of OMS tasks. However, there is no explicit guidance on when to use it instead of hcloud_list_oms_sync_tasks or hcloud_show_oms_task.

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