hcloud_list_scaling_policies

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: it doesn't state that results are scoped to a scaling group and region, nor how pagination via limit behaves.

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?

A single front-loaded sentence with no filler or redundancy. It is terse rather than bloated, though the terseness comes at the cost of omitted scoping 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?

For a list tool requiring scaling_group_id and region and returning no output schema, the description should mention that the listing is scoped to a specific scaling group and region and what limit does. Without annotations covering these semantics, the omission leaves 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 coverage is 100%, so region, scaling_group_id and limit are already documented in the schema. The description contributes no additional meaning about parameter formats or interactions, which is the baseline 3 for full schema coverage.

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?

"List AS (Auto Scaling) policies" gives a clear verb plus resource and expands the abbreviation, so the purpose is unambiguous. It does not differentiate itself from nearby siblings such as hcloud_list_scaling_configs or hcloud_show_scaling_policy, so it stops short of a 5.

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?

There is no guidance on when to use this versus the single-policy show tool or the scaling-config list, and no prerequisite context. The agent must infer everything from the name and schema.

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