hcloud_list_vpcs

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 note on pagination behavior despite limit/offset parameters, no indication of result ordering, and no statement of what the response contains.

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?

Five words, front-loaded with the verb and resource, no filler. It is efficient, though brevity here shades into under-specification rather than disciplined editing.

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 paginated list tool with full schema coverage and complete annotations, this is marginally adequate. An agent can call it correctly, but receives no signal about pagination semantics or result shape.

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 the schema already documents region, limit, and offset, and the baseline is 3. The phrase "in the region" merely restates the required region parameter and adds no format or constraint detail 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?

"List VPCs in the region" states a specific verb (List) and resource (VPCs) plus a scope qualifier. It is distinguishable from siblings like hcloud_list_subnets or hcloud_list_vpn_gateways purely by resource name, though it never explicitly contrasts with them.

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 when-to-use or when-not-to-use guidance. It does not say whether this is the right tool for enumerating VPCs vs. inspecting one (hcloud_show_vpc), nor does it mention any prerequisites or alternative listing paths.

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