hcloud_list_servers

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

Annotations already declare readOnly/destructive/openWorld, so the bar is lower, and the description still adds real behavioral detail: name_contains is applied client-side after fetching, sort defaults to 'name', and the underlying call is GET /servers. It stops short of explaining how post-fetch filtering interacts with pagination (each page filtered independently), which is the one behavior an agent could get wrong.

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?

Three short sentences, purpose first, the filter/sort behavior second, the sibling routing last — nothing redundant and no filler.

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 five optional parameters, no output schema, and no pagination guidance, an agent still doesn't know the response shape or whether results are paginated beyond per_page's max of 50. The description is adequate for selection but thin for correct invocation of the paging path.

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 only 40%, and the description reinforces the two fields the schema already describes (name_contains as a client-side filter, sort's 'name' default) while leaving page and per_page completely undocumented in both places. Helpful but not compensating for the coverage gap.

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 Hetzner Cloud servers") and immediately distinguishes itself from the sibling hcloud_list_servers_raw by naming the divergence (hand-tuned vs generator-built). An agent can pick between the two without opening either schema.

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?

Explicitly routes the agent: use the raw sibling for unfiltered output, this one for the filtered/sorted variant. It doesn't cover when to prefer label_selector over name_contains, but the core alternative is named with a condition.

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