hcloud_show_subnet

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered. The description adds nothing beyond that — no statement about failure behavior when the ID is unknown, cross-region lookup semantics, or response shape — making it largely redundant with the structured metadata.

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 the operation and target front-loaded, and no filler or repetition of the tool name. Nothing in it is wasted, even if more could have been said.

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 lookup tool with no output schema, the description should at minimum sketch what details are returned and how a caller resolves the required region/subnet_id pair. Neither is present, so an agent knows the intent but not the result or the lookup semantics.

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 both 'region' and 'subnet_id' are documented in the schema, and the baseline is 3. The description adds no extra meaning, such as whether region must correspond to the subnet's home region or what identifier format subnet_id expects.

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 states a specific verb and resource: 'Get details of a specific subnet', which is unambiguous about the read-by-identifier operation. It does not, however, distinguish this from the very similar sibling hcloud_list_subnets, so an agent must infer the singular-vs-list split from the name alone.

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?

The word 'specific' implies a single-subnet lookup as opposed to listing, which is a weak but real usage signal. There is no explicit when-to-use, no prerequisite note (e.g. that region must match the subnet's region), and no named alternative such as hcloud_list_subnets.

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