hcloud_list_vpn_customer_gateways

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: it does not describe pagination semantics, result ordering, whether count/total is returned (there is no output schema), or permission requirements, and 'optional filters' loosely mislabels limit/offset, which are pagination, not filters.

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 sentence with zero waste and the resource front-loaded after the verb. Its brevity is appropriate, though the phrase 'optional filters' is filler that does not map to any actual parameter.

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 simple read-only list tool with full schema coverage and read annotations, the description is minimally adequate. It leaves the required region parameter unaddressed in prose and gives no indication of return shape or pagination behavior, but nothing critical is missing for correct invocation.

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 three parameters are documented in the schema; baseline is 3. The description adds no meaning beyond that and does not clarify that region is the required scoping parameter or how limit/offset interact.

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 customer gateways (CGWs)'. The parenthetical abbreviation is helpful, but nothing distinguishes it from the sibling vpn list tools (hcloud_list_vpn_gateways, hcloud_list_vpn_connections, hcloud_list_vpn_ipsec_policies) beyond the resource name itself.

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?

Only 'with optional filters' hints at usage. There is no guidance on when to use this versus the sibling show/list VPN tools, no note that region is required, and no mention of how pagination via limit/offset should be applied.

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