hcloud_list_vpn_ipsec_policies

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no note on pagination, result volume, or region-scoped visibility, which for an open-world list operation is the kind of context that would be valuable.

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?

It is a single four-word phrase with nothing wasted and nothing front-loaded incorrectly. That said, the brevity reflects under-specification rather than disciplined concision.

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?

With no output schema, the description should at least signal what a policy record looks like or how results are returned, and it says nothing. For a list tool with one region-scoped parameter and full annotation coverage the gap is not severe, but the definition is bare.

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?

There is a single required parameter and schema description coverage is 100%, so the schema carries the full burden and the baseline of 3 applies. The description does not explain what 'region' means here (scoping dimension vs. filter value) or whether it accepts names or IDs, so it adds no meaning beyond the schema.

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 gives a verb ('List') plus a specific resource ('VPN IPsec policies'), so the basic purpose is readable and the resource name distinguishes it from the sibling hcloud_list_vpn_ike_policies. However, it is essentially a decoded restatement of the tool slug with no further scope detail, so it sits at minimum-viable rather than clearly differentiated.

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 when-to-use guidance, no mention of the IKE-policy sibling as an alternative, and no stated prerequisites. An agent must infer from the name alone that this is the IPsec-policy listing endpoint rather than the IKE one.

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