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

The readOnlyHint annotation already establishes that this is a safe read, and the GET /networks reference reinforces that. The description adds useful context about what a network record contains (IP ranges, subnets, routes), but says nothing about pagination behavior or result-set size, which matters given page/per_page parameters.

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?

Two short sentences, zero filler, with the resource and returned data front-loaded and the API endpoint trailing as supporting detail. Nothing should be cut.

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 list endpoint with full schema coverage and a readOnlyHint, the description is nearly sufficient: it conveys scope, returned fields, and the backing API. It only misses pagination/result-size expectations and any list-vs-get disambiguation.

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 every parameter (name, page, per_page, label_selector) is already documented in the schema, including the label-selector idiom. The description adds no parameter-level meaning beyond that, so the baseline of 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?

States a specific verb ('List') and resource ('private networks') and names the fields returned (IP ranges, subnets, routes), plus the underlying API call (GET /networks). This is enough to separate it from most siblings, though it never explicitly contrasts with the singular hetzner_get_networks.

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?

Usage is only implied: the verb 'List' suggests enumerating all networks, but there is no statement of when to prefer this over hetzner_get_networks, nor any hint that name/label_selector can narrow results. A reader can infer the intent but gets no routing guidance.

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