hcloud_show_vpc

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 fully covered and the lower bar applies. The description adds nothing on top: no note that this is a non-mutating lookup, no indication of whether a missing VPC errors or returns empty, and no mention that region scopes the lookup (the same VPC ID may not exist across regions).

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?

One short sentence with no padding and the resource in focus — structurally clean. It is arguably too terse rather than too long, but nothing is wasted or buried.

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?

This is a simple two-parameter read with no output schema, so the description carries the burden of explaining the return shape and the region/ID relationship. It does neither, and it never routes the agent to hcloud_list_vpcs for enumeration, leaving the definition insufficient for confident invocation sequencing.

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% (both required parameters are documented, albeit tersely as 'Region' and 'VPC ID'), which sets the baseline at 3. The description adds no meaning beyond the schema — nothing on ID format, on whether region must match the VPC's owning region, or on accepted region naming conventions.

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 names a verb and resource ('Get details of a specific VPC'), which is enough to distinguish a single-resource fetch from a browse operation in the abstract. However, it never mentions the sibling hcloud_list_vpcs, and 'details' is undefined, so the boundary between fetching one VPC and listing all VPCs rests entirely on the reader's inference from the word 'specific'.

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 exclusion pointing to hcloud_list_vpcs for discovery, and no statement of prerequisites such as needing a VPC ID obtained from a list call first. The agent must guess the intended call sequence.

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