hcloud_show_oms_task

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds essentially no behavioral context beyond that label - nothing about error behavior for an unknown task_id, region scoping requirements, or what the returned 'details' comprise.

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 zero waste and the acronym expanded for clarity. It is efficient, though the brevity leaves little substance beyond what the name already conveys.

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 two-parameter read-only lookup with annotations covering safety, this is minimally adequate: the agent knows what it fetches and which inputs are required. Missing is any sense of the response content (no output schema exists) or failure modes, which would matter for a get-by-ID call.

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 the baseline is 3. However, the schema only labels the parameters ('Region', 'Task ID') with no format hints, and the description does not compensate by explaining task_id format or whether region must match the task's region.

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 ('Get details') and resource ('a specific OMS task'), and the word 'specific' plus the required task_id distinguish it from the sibling hcloud_list_oms_tasks. It stops short of naming the list tool explicitly, but the singular/plural split is inferable.

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?

Usage is only implied: an agent can guess this is the follow-up call after listing tasks to get one task's details. There is no explicit statement of when to use this versus hcloud_list_oms_tasks or hcloud_list_oms_sync_tasks, and no prerequisites such as needing an existing task_id in the given region.

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