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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description still adds value by listing exactly which fields come back (type, image, IPs, volumes, networks, protection flags) and by citing the backing endpoint GET /servers/{id}. It does not discuss error behavior for a nonexistent id, but that is a modest gap.

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 compact sentences, zero padding, and the payload contents are front-loaded before the API endpoint reference. Every clause earns its place.

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?

With no output schema, the description usefully enumerates the response contents, which is the main completeness risk for a getter. Only minor gaps remain (error/not-found behavior, whether related resources are embedded or referenced).

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 a single documented integer parameter, so the schema carries the parameter burden. The description adds nothing about server_id syntax beyond the endpoint template {id}, which matches the baseline of 3 when the schema does the heavy lifting.

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?

Specific verb ("Fetch") plus resource ("a single server") and an enumeration of the returned sub-resources (type, image, IPs, volumes, networks, protection flags). The word "single" implicitly distinguishes it from hetzner_list_servers, but no sibling is named explicitly.

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?

Usage is implied by the singular-resource phrasing and the required server_id, but there is no explicit when-to-use guidance and no reference to alternatives such as hetzner_list_servers for discovering ids or hetzner_get_server_metrics for performance data.

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