hcloud_list_scaling_policies

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

With no annotations, the description carries full burden but only states 'List', implying a read-only operation. It does not disclose potential pagination, rate limits, or whether the operation is safe (though implied). The description lacks behavioral details 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 single phrase is concise but under-specified. It lacks necessary details to be fully informative, such as the requirement for a scaling group ID. The sentence does not 'earn its place' as it provides minimal value.

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 tool's simplicity (3 parameters, no output schema), the description should at least mention return value nature (e.g., list of policies) or pagination. It is incomplete for an AI agent to reliably invoke without guessing.

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% (all three parameters have descriptions). The tool description adds no additional meaning beyond restating the resource; it does not explain parameter relationships or constraints. Baseline 3 is appropriate as the schema already does the heavy lifting.

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 specifies the verb 'List' and the resource 'AS (Auto Scaling) policies', clearly identifying its function. It distinguishes from siblings like hcloud_list_scaling_groups by naming the specific resource type, though it omits that listing is per scaling group (implied by required parameter).

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?

No guidance on when to use this tool vs others (e.g., hcloud_show_scaling_policy for a single policy, or other list tools). No context on prerequisites or alternatives is provided.

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