hcloud_list_mrs_clusters

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety and idempotency are covered structurally. The description adds no behavioral context at all — no pagination behavior, no result-set size, no ordering, no error conditions for an invalid region.

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?

A single short sentence with zero filler and the resource front-loaded. It is efficient, but the brevity reflects under-specification rather than disciplined editing.

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 paginated list tool with no output schema, an agent needs to know what fields come back and how paging behaves; neither is described. With only a title-equivalent sentence, the definition is too thin to call the tool confidently beyond its trivial case.

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% (limit, offset, region each documented), so the schema carries the parameter burden. The description adds no extra meaning about region scoping or how limit/offset interact with the listing, which is acceptable but unremarkable given full coverage.

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 and resource (list MRS clusters) and expands the acronym MRS to MapReduce Service, which is helpful. However, it adds essentially nothing beyond the tool name, and gives no indication of scope (project-wide? region-scoped?) or how it differs from hcloud_show_mrs_cluster or hcloud_list_mrs_flavors.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. region required), and no routing to alternatives such as hcloud_show_mrs_cluster for details on a single cluster. The only reason a reader can infer usage is the literal word 'List'.

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