hcloud_list_er_routers

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safe read-only nature is covered elsewhere. The description adds no behavioral context beyond restating that this lists routers; it does not mention pagination, result ordering, or regional scoping behavior.

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?

The description is a single front-loaded sentence with no redundant wording, which suits a simple list operation. It is terse but not unclear, and nothing in it is wasted.

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 strong annotations, the definition is minimally sufficient. However, it lacks any mention of regional scope or pagination behavior, and there is no output schema to explain the returned router list.

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%, covering region, limit, and offset, so the schema already carries parameter meaning. The description adds no parameter-specific detail such as whether region is mandatory or how pagination should be used; baseline 3 is appropriate.

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 clear verb and resource: "List ER (Enterprise Router) routers", and it expands the ER acronym so the agent knows the object type. It is distinguishable from the sibling hcloud_show_er_router by being a list operation, but it does not further differentiate from hcloud_list_er_route_tables or hcloud_list_er_attachments.

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 description states only that this is a listing operation. It gives no explicit when-to-use guidance, no prerequisites, and no alternatives such as hcloud_show_er_router for a single router or the route-table/attachment list tools.

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