hcloud_get_location

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is fully covered. The description adds nothing beyond them — the only extra text is a broken markdown anchor pointing at the API docs, which conveys no behavioral information.

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?

Very short and front-loaded, but the second sentence is a dangling reference-style link that resolves to nothing useful, so one of only two sentences is effectively wasted.

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?

No output schema exists, so the description carries the burden of explaining what a Location returns (name, description, country/city, network zone, coordinates). It says only that it returns a Location, leaving the agent unable to predict the response shape for what is otherwise a trivially simple tool.

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?

Single parameter with 100% schema description coverage ("ID of the Location", int64, min 1), so the schema fully documents it. The description adds no extra meaning, which is the expected baseline 3 when schema coverage is complete.

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 ("Get a Location"), so an agent can tell it retrieves a single location rather than listing them, but it offers no elaboration on what a Location is or how it differs from the numerous other hcloud_get_* singular lookups.

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 guidance on when to use this versus hcloud_list_locations or hcloud_get_datacenter, which both surface location data. No prerequisites, no note that an ID must be known in advance (e.g., obtained from list_locations).

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