hcloud_list_pools

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered without description help. The description adds nothing about pagination, result ordering, or what 'pools' contain, so it contributes no behavioral context beyond the structured fields.

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?

A single short sentence with the resource front-loaded and zero filler; nothing is redundant. Its brevity is achieved without obscuring the resource identity, thanks to the clarifying parenthetical.

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 two-parameter read-only list tool with rich annotations and no output schema, this is minimally adequate. An agent knows what is listed but not whether results are scoped to a specific load balancer or how to page past limit, leaving a real gap for a list operation.

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 only two parameters (limit, region), so the schema already documents both fields. The description adds no meaning about region scoping or how limit interacts with pagination, 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?

The description gives a specific verb plus resource: "List ELB backend server groups (pools)". The parenthetical disambiguates the otherwise vague tool name 'pools' (which could be node pools or scaling pools) toward ELB backend server groups, which is genuine value. It stops short of naming a sibling such as hcloud_list_load_balancers or hcloud_list_node_pools to positively differentiate.

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 statement of when to use this tool versus the many sibling list tools, no mention that a region is mandatory, and no note that a load balancer context may be needed. The agent must infer the use case entirely from the one-line purpose.

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