hcloud_list_networks

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. Beyond that the description adds nothing: it does not mention the pagination soft-cap, how auto_paginate merges pages, default page size, or the exact-match semantics of the name filter.

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?

It is short and front-loaded, but the title line 'List Networks' is redundant with the tool name and the closing sentence about URI parameters is vague filler rather than useful guidance.

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 list endpoint with a fully documented schema and clear read-only annotations, the description is minimally adequate, but it omits any note on pagination behavior (auto_paginate defaults to true, soft-cap) that an agent would want before calling.

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 schema already documents name, label_selector, page, per_page, sort, and auto_paginate. The description's generic 'URI parameters' sentence adds no meaning beyond that, 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 states the verb (list) and resource (Networks), and 'List multiple' implicitly distinguishes it from hcloud_get_network for a single entity. However, 'List multiple [Networks]' largely restates the tool name, and it never explicitly contrasts itself with siblings like hcloud_get_network, hcloud_get_network_members, or hcloud_list_networks_actions.

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?

The only usage hint is 'Use the provided URI parameters to modify the result,' which does not say when to use this tool versus related read tools (single-network get, members, actions). No exclusions, prerequisites, or alternative routing are given.

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