hcloud_list_servers_raw

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds nothing beyond restating the name——it does not disclose what "raw" means (raw API payload vs. normalized objects), nor the auto_paginate soft-cap behavior that determines whether "all" servers are actually returned.

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 short sentences, front-loaded with the operation. The second sentence is largely redundant with the first, but there is no padding or noise.

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 7-parameter list tool with no output schema, no annotation gaps but a confusing "_raw" variant amid many list/get siblings, the description should clarify response shape and sibling selection. It does neither, leaving the agent to infer the distinction entirely.

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 name, status, sort, page, per_page, label_selector, and auto_paginate are all documented in the schema. Baseline 3 applies; the description contributes no additional parameter semantics (e.g., label selector syntax or the interaction between auto_paginate and per_page).

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?

The description gives a clear verb and resource ("List Servers ... Returns all existing Server objects"), so the basic operation is understandable. However, it never explains the "_raw" qualifier or how this differs from the sibling hcloud_list_servers and hcloud_get_server_raw, which is the main thing an agent needs to disambiguate here.

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 when-to-use guidance, no exclusions, and no mention of alternatives. With a near-identical sibling (hcloud_list_servers) present, the description leaves the agent with no basis for choosing between them.

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