hcloud_server_add_to_placement_group_action

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

Annotations only cover the safety profile (not read-only, not destructive, open-world); the description adds real behavioral detail beyond that — the powered-off requirement and the specific 422 failure codes (server_not_stopped, already_in_placement_group). It doesn't describe the returned action object or what `wait` does, which is the remaining gap.

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?

Front-loads the action and its precondition, and the error table is efficient, machine-readable content. The heading restates the body sentence verbatim, a small redundancy, but nothing is bloated.

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 mutation action tool with no output schema, the description covers the critical thing an agent needs — the precondition that gates success — plus documented failure modes. It omits return-value/polling behavior, but annotations and schema already establish the safety profile and the `wait` flag.

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 coverage is 67% and all three parameters already carry descriptions in the schema, so the baseline applies. The description adds no information about `id`, `placement_group`, or the `wait` polling flag — reasonable but no added value on parameters.

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?

States a specific verb and resource ('Adds a Server to a Placement Group'), making it trivially distinguishable from its sibling hcloud_server_remove_from_placement_group_action. The heading line duplicates the body sentence, so it earns less than full marks, but an agent knows exactly what it does.

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?

Gives a hard precondition ('Server must be powered off') that tells the agent when this call will fail, plus the two operation-specific errors. It stops short of naming alternatives (e.g. power off first, or use the remove counterpart), so it's clear context rather than full routing guidance.

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