hcloud_get_networks_actions_id

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 covered. The description contributes nothing further — notably it does not mention that polling can block until success/error or timeout, which is the one behavioral trait that matters most here.

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?

Two short sentences with no filler and the verb front-loaded. It is efficient but borders on redundant with the tool title, so it is concise without being informative.

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?

With only two parameters, full schema coverage, and annotations covering safety, the definition has room to say something — yet it omits the network scope, the difference from sibling action getters, and the effect of `wait`. For a tool competing against dozens of near-identical action lookups, that is a real gap.

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 both `id` and `wait` are already documented in the schema, giving a baseline of 3. The description adds no meaning beyond that — it doesn't clarify the ID namespace (network-scoped action IDs) or the polling/timeout semantics.

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 Action / Returns a single [Action]" restates the name and title without adding scope. Critically, it drops the network scoping implied by the tool name, so it reads as a generic action getter indistinguishable from siblings like hcloud_get_action, hcloud_get_network_action, and hcloud_get_primary_ips_actions_id.

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 when-to-use guidance and no alternatives named. An agent cannot tell from this text whether to use this, hcloud_get_network_action, or the list variant hcloud_get_networks_actions, nor what the `wait` parameter implies about using hcloud_wait_action instead.

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