hcloud_show_scaling_policy

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

The annotations establish that the operation is read-only, idempotent, and open-world, and the description is consistent with them. Beyond indicating a lookup, the description adds no behavioral context such as the source of the details, response scope, or handling of an unknown policy ID.

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?

The single short sentence is direct, front-loaded, and contains no unnecessary wording. Its brevity is appropriate for a simple show operation, although the surrounding definition remains minimal.

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 operation, the schema and annotations provide enough information to make a basic call. With no output schema, however, the description could add more value by indicating what policy details are returned or how this tool relates to hcloud_list_scaling_policies.

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 required parameters are already documented, establishing the baseline score. The description's reference to a specific policy aligns with scaling_policy_id but adds no further meaning about region selection or ID discovery.

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 clearly states the action and resource: retrieving details for a specific auto-scaling policy. It implies a single-item lookup but does not explicitly distinguish this tool from hcloud_list_scaling_policies or other scaling-related siblings.

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 phrase 'a specific AS policy' implies use when the caller already has a policy ID and wants its details. There is no explicit guidance on when to use the list tool first, when this tool is unnecessary, or any prerequisites.

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