hcloud_list_datacenters

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 fully covered by structured data. The description's added value is the deprecation timeline, which is real and useful; it says nothing about pagination behavior or the auto-merge soft-cap, despite 'Returns all' being dependent on that default.

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, with the deprecation warning placed prominently before the return statement. The opening 'List Data Centers' line merely restates the tool name, a small amount of waste, but nothing else is padded.

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 simple read-only list endpoint with full schema coverage and annotations carrying the safety profile, the description covers purpose and the critical lifecycle status. The only meaningful gap is not pointing at a replacement or sibling resource, which matters given the imminent removal date.

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 all five parameters (name, page, sort, per_page, auto_paginate) are already documented in the schema, including defaults and the soft-cap note. The description adds no filter, sort, or pagination semantics beyond that, so the baseline 3 applies.

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 ('List Data Centers' / 'Returns all Data Centers'), which cleanly distinguishes it from the singular sibling hcloud_get_datacenter. It does not explicitly name that sibling or contrast with hcloud_list_locations, but the plural-list scope is unambiguous from the name-plus-description pairing.

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 deprecation notice ('deprecated as of 01 June 2026 and will be removed after 01 October 2026') is a genuine when-to-use signal, warning the agent to prefer alternatives for new work. However, no alternative is actually named (e.g. locations vs. datacenters, or a replacement endpoint), so the guidance is implied rather than actionable.

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