hcloud_get_volume_action

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context with the deprecation notice and changelog link, which an agent would not otherwise know; it does not explain the 'wait' polling semantics, but the schema covers that parameter.

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 deprecation warning before the functional statement, which is the right ordering for an agent deciding whether to call it. Slightly redundant between the heading and 'Returns a specific Action for a Volume', but no padding.

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 getter with full schema coverage and no output schema, the description is adequate. However, it points to a changelog rather than naming the replacement endpoint, leaving the agent without an actionable migration path for a deprecated operation.

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% — both id and action_id are documented, and wait is documented with its polling behavior. The description adds no parameter meaning beyond the schema, 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?

States a specific verb and resource ('Get an Action for a Volume') and clarifies it returns a specific Action, which distinguishes it from list-style siblings such as hcloud_list_volume_actions. It does not explicitly contrast itself with hcloud_get_action or hcloud_get_volumes_actions_id, so it stops short of full sibling differentiation.

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?

The deprecation notice is a meaningful usage signal (avoid this endpoint), but the description never says when to prefer hcloud_get_action, hcloud_get_volumes_actions_id, or hcloud_wait_action, nor what to migrate to. Usage is only implied.

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