hcloud_list_members

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, and the description adds nothing beyond that. It says nothing about pagination behavior implied by the limit parameter, whether members include health status, or the shape of results for a tool with no output schema.

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 front-loaded sentence with zero padding. Nothing is wasted, though the extreme terseness leaves the definition doing no extra work.

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 read-only list tool with full schema coverage and annotations carrying the safety profile, the basics are covered. The remaining gaps — pagination semantics and what a member record contains — matter more here because there is no output schema to fall back on.

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 the baseline is 3. The description only reinforces pool_id via the phrase 'in an ELB pool'; it adds no meaning for region (whether it must match the pool's region) or limit (page size vs. cap).

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 (List) and resource (backend members) scoped to an ELB pool, which separates it from sibling hcloud_list_pools that lists the pools themselves. It does not name a sibling or explain the relationship explicitly, so it stops short of 5.

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?

Implicit usage is clear from 'in an ELB pool' — the agent knows a pool_id is a prerequisite and that this is the drill-down from a pool listing. However, there is no explicit when-to-use versus hcloud_show_load_balancer_topology or other pool-adjacent tools, and no exclusions or ordering guidance.

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