hcloud_get_iso

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered externally. The description adds nothing beyond them — no note on error behavior for a nonexistent id, no mention of what identifiers the returned object exposes (which matters since ISOs are passed to hcloud_server_attach_iso_action).

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?

It is short and front-loaded, but the second sentence ("Returns a specific ISO object.") is a pure restatement of the first and earns no place. Brevity here comes from under-specification rather than efficient communication.

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 read-only lookup with full annotation and schema coverage, this is minimally sufficient: the agent knows it fetches one ISO by id. It stops short of explaining how the fetched object is used downstream (attaching to a server) or how to discover ids, leaving a real gap in a large sibling set.

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% and the single required parameter (id, int64, min 1) is fully documented in the schema with an example. The description adds no meaning beyond that, 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?

"Get an ISO" is a specific verb plus resource, and the second line clarifies it returns a single ISO object. However, both sentences essentially restate the tool name and neither distinguishes it from the sibling hcloud_list_isos (which returns many ISOs) or explains what an ISO is used for in this API.

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?

No guidance on when to use this versus hcloud_list_isos or hcloud_list_images, no prerequisites, and no note that an ISO id must be obtained first (e.g., from the list endpoint). The agent must infer the entire selection context.

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