hcloud_show_sms_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 structurally. The description contributes nothing behavioral beyond that — no indication of what the response contains, whether a missing task errors or returns empty, or any pagination/consistency notes.

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 or redundancy. It is efficient, though its brevity leaves no room for structure that would carry usage or behavioral cues.

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 two-parameter read tool with full schema coverage, no output schema, and annotations carrying safety, the description is minimally sufficient to pick the tool. It still leaves out how to obtain a task_id and what details are returned, which a caller of a resource-detail endpoint would want.

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 baseline is 3. The description adds no meaning to the two parameters — it does not say what form a task_id takes or whether region must match the task's home region — so it neither compensates nor detracts.

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 names a specific verb ("Get details") and a specific resource (an SMS Server Migration Service migration task), and the word "specific" implicitly contrasts with the sibling hcloud_list_sms_tasks. It also expands the SMS acronym so the agent knows the domain, though it never names the list tool it complements.

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 when-to-use guidance: nothing says to call hcloud_list_sms_tasks first to discover a task_id, nothing explains when to prefer this over hcloud_show_sms_server, and no prerequisites are given. The agent must infer the list-then-show workflow from the sibling names alone.

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