hcloud_show_scaling_policy

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

With no annotations provided, the description carries the full burden. It indicates a read operation ('Get') but does not disclose any behavioral traits such as authentication requirements, rate limits, error conditions, or whether the operation is safe. The description is minimal and lacks detail beyond the basic 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?

The description is a single sentence with no wasted words, but it lacks structure such as front-loading or separating important context. It is concise to the point of being sparse, omitting possible helpful details.

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?

Given the lack of an output schema, the description provides minimal context about what 'details' entails. It does not mention the format or fields of the response, prerequisites, or hints about supported regions. For a simple retrieval tool, it is adequate but not comprehensive.

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 100% (both parameters described in schema). The description adds no additional meaning or context for the parameters 'region' and 'scaling_policy_id' beyond what the schema provides. Baseline score of 3 is appropriate.

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 'Get details of a specific AS policy', using a specific verb ('Get') and resource ('AS policy'). It distinguishes from sibling tools like hcloud_list_scaling_policies, which lists policies, and other show tools for different resources.

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 description implies usage for retrieving a specific policy's details but provides no explicit guidance on when to use this tool versus alternatives like hcloud_list_scaling_policies or other show tools. No when-not or exclusion information is given.

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