hcloud_list_vpn_connections

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 essentially nothing beyond that — no pagination behavior, default limit, region scoping, or volume-of-results context — despite 'optional filters' being the only substantive claim.

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 short, front-loaded sentence with no filler. Nothing is wasted, but the brevity borders on under-specification rather than crispness.

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?

The tool is simple and the schema is fully described, so little is strictly missing. However, with no output schema and no mention of pagination semantics or the required region scope, the description leaves an agent to infer how results are returned and bounded.

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%, so all four parameters (limit, offset, region, vgw_id) are already documented in the schema. The description's mention of 'optional filters' only hints at vgw_id filtering and adds no syntax or default-value detail, so baseline 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 and resource ('List VPN connections'), which is clearly distinguishable from siblings like hcloud_show_vpn_connection and hcloud_list_vpn_gateways. The phrase 'with optional filters' is vague but doesn't obscure the core purpose.

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?

'With optional filters' implies that this is the enumeration/filtering tool, but no explicit when-to-use guidance is given. It never states the relationship to hcloud_show_vpn_connection (detail lookup) or hcloud_list_vpn_gateways, nor any exclusions.

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