hcloud_get_datacenter

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context with the deprecation timeline and removal date, which affects whether an agent should rely on this tool at all.

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?

Front-loaded with the deprecation warning, then the one-line purpose. Minimal waste, though 'Returns a single [Data Center](#tag/data-centers)' is thin and the anchor link adds little for an agent.

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 single-resource read with full annotation coverage and a fully documented schema, this is close to sufficient. With no output schema, though, the description does not sketch the return shape beyond 'a Data Center', leaving the agent to guess at fields like location or server types.

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 coverage is 100% and the single 'id' parameter is fully documented in the schema, so the description adds nothing beyond it. Baseline 3 applies when the schema carries parameter semantics entirely.

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 and clarifies the scope as 'a single Data Center', which implicitly contrasts with the sibling hcloud_list_datacenters. It does not explicitly name the alternative, but the singular versus list distinction is inferable.

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 with concrete dates functions as a strong when-not-to-use signal, arguably the most actionable guidance here. However, it never names a replacement or tells the agent when fetching a single datacenter is the right call versus listing.

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