hcloud_list_policies

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and mutability are covered. The description contributes only the system/custom scope note and says nothing about result volume, pagination defaults, or how the single limit parameter affects returns. With annotations carrying the behavioral load, a 3 is appropriate.

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 clause with the resource and its scope; nothing is padded. It is slightly under-informative rather than verbose, which keeps it efficient but leaves no room for routing guidance.

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 one-parameter, read-only list tool with full annotation coverage, the description is minimally sufficient to call correctly. It falls short on disambiguating against the numerous sibling policy-listing tools, which is the main open question an agent would have here.

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% and the sole parameter (limit) is documented as 'Max results'. The description adds no format, default, or maximum guidance 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 (List) and resource (IAM policies), and adds scope detail by noting both system and custom policies are returned. This separates it from the many other '*_policies' siblings such as hcloud_list_cbr_policies and hcloud_list_scaling_policies by naming the IAM domain, though it does not explicitly contrast with hcloud_list_user_policies, which covers a related resource.

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention of what it does not cover. The 'system and custom' phrase implies it returns everything without filtering, but the agent must infer that rather than being told.

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