hcloud_list_locations

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only "Returns all", and even that is ambiguous given the schema's auto_paginate default and soft-cap behavior — it does not clarify whether results are merged pages, sorted order, or rate-limited.

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?

Extremely short and front-loaded, which suits a simple list endpoint. The second sentence largely duplicates the first, so it is efficient but not free of waste.

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 parameterless-by-default list tool with full schema coverage and complete safety annotations, the description is minimally sufficient. It is missing what a Location represents and how results are returned (merged pages vs paginated), which matters because auto_paginate defaults to true.

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% with 5 optional params, so the schema already documents name filtering, paging, sorting and auto_paginate. The description contributes no additional semantics — notably it does not explain the auto_paginate soft-cap tradeoff, which is the most consequential parameter.

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 Locations / Returns all Locations" identifies the verb and resource but is essentially a restatement of the tool name hcloud_list_locations. It does convey the list-all (non-single) shape, but nothing distinguishes it from siblings such as hcloud_get_location or hcloud_list_datacenters beyond the name itself.

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 statement of when to use this tool versus hcloud_get_location (single location by ID/name) or hcloud_list_datacenters, and no prerequisites or exclusions are given. The only implicit cue is "all" in the body text, which the agent must infer.

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