hcloud_get_network_members

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safe read-only nature is conveyed structurally. The description adds nothing behavioral beyond that — no note on pagination semantics, result set size, or that the network must exist — so it neither helps nor contradicts.

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?

Short and front-loaded, but the trailing sentence 'Use the provided URI parameters to modify the result' is boilerplate that does not earn its place. The rest is a restatement of the title plus one clarifying sentence.

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 read-only, fully-documented paginated list endpoint this is adequate, and annotations cover the safety profile. However, with no output schema the description never hints at what a 'member' looks like (server/load balancer with ip, status, subnet), leaving the agent to infer the response shape.

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?

With 100% schema description coverage, the schema already documents id, page, per_page, sort, type, status and subnet in detail. The description's generic 'URI parameters' phrasing adds no meaning beyond the schema, 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+resource: 'List the resources attached to a specific Network', which is more precise than the name alone. It does not explicitly distinguish itself from near-neighbors like hcloud_get_network or hcloud_list_networks, so an agent must infer the difference.

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?

No statement of when to use this tool versus alternatives such as hcloud_get_network (which returns network details) or hcloud_list_networks. The only guidance is the vague 'Use the provided URI parameters to modify the result', which is not actionable and names no conditions or exclusions.

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