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

readOnlyHint=true already establishes the safe read-only profile, so the description's main addition is the REST endpoint mapping. It says nothing about 404/not-found behavior, whether the id must exist, or what the payload contains, so it adds limited behavioral context beyond the annotation.

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 core action front-loaded and the API mapping as supporting detail. Nothing here needs trimming.

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 trivial one-parameter read tool with full schema coverage and a readOnlyHint annotation, the description covers what is needed to invoke it correctly, and no output schema means return values need not be explained. It is slightly generic ('a single resource' rather than naming networks) but functionally complete.

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% and the single 'id' parameter is fully documented in the schema, so baseline 3 applies. The description's 'by id' merely restates the parameter rather than adding format or range guidance.

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 and resource ('Fetch a single resource by id') and pins it to the concrete REST call 'GET /networks/{id}', so the agent knows this is a single-network lookup rather than a list. It does not explicitly name the sibling hetzner_list_networks, but the 'single resource by id' framing distinguishes it from the list-family tools well enough.

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 phrase 'by id' implies you must already hold an id, which is the only real usage condition, but there is no explicit when-to-use/when-not statement or pointer to alternatives such as hetzner_list_networks for discovery. Usage is inferable rather than stated.

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