hcloud_list_rgc_control_policies

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered by structured data. The description contributes nothing beyond that: no indication of whether the region argument scopes a global or regional endpoint, no pagination behavior, no note that an empty result is possible for regions without RGC.

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 single short phrase is front-loaded and contains no filler, so nothing needs trimming. However, its economy comes from under-specification rather than discipline — it fits in one line only because it says almost nothing.

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 tool with no output schema and 100% schema coverage, the description is technically callable but incomplete: it never expands RGC, never says what a returned control policy represents, and never clarifies whether region is the only scoping dimension. The structured fields cannot fill that gap.

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 all three parameters (region, limit, offset) are documented in the schema, which sets the baseline at 3. The description adds no extra meaning such as accepted region identifier formats or default/maximum for limit, so it neither helps nor hurts.

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?

"List RGC control policies" restates the tool name almost verbatim, adding no scope, filtering, or resource detail. The acronym RGC is never expanded, so an agent has no way to know what domain these policies belong to or how they relate to the many other policy-listing siblings (hcloud_list_policies, hcloud_list_cbr_policies, hcloud_list_l7_policies).

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 exclusions, and no mention of any alternative among the dozens of sibling list tools. An agent must guess from the name alone whether to select this over hcloud_list_policies or hcloud_list_cbr_policies.

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