hcloud_list_subnets

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered without the description. The description adds nothing beyond that—no pagination behavior for the limit parameter, no ordering, no note on what an empty list means. No contradiction with annotations, but no added value either.

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?

Two words, so there is zero waste, but this is under-specification rather than conciseness—nothing is front-loaded because nothing is stated. It is not verbose, just empty.

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 list tool with a required region filter, an optional VPC filter, a result limit and no output schema, the description should say what is returned and how paging/limits behave. None of that is present, leaving the agent to guess at result shape and 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 the baseline is 3 even though the description says nothing about the three parameters. The schema's own text ("Max results", "Region", "Filter by VPC ID") carries the meaning; the description neither helps nor misleads.

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 subnets" restates the tool name (hcloud_list_subnets) rather than stating scope, what a subnet is here, or how it relates to the sibling hcloud_show_subnet. It is technically a verb+resource, but adds nothing an agent could not infer 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?

No when-to-use guidance, no mention of the alternative hcloud_show_subnet for single-resource retrieval, and no note that region is mandatory while vpc_id narrows the result set. The agent is left to infer filtering behavior from the schema.

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