hcloud_list_drs_quotas

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the description's only remaining job would be to add behavioral context — but it adds none. It does not say whether the response is per-region, whether results are paginated, or whether quotas can be zero/absent for a region. It also does not contradict the annotations.

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?

One short sentence with zero padding, and the verb and resource are front-loaded. Its brevity is also its weakness — nothing is wasted, but nothing extra is spent on orientation either.

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 single-parameter, read-only list tool with full annotation coverage and no output schema, this is close to the minimum acceptable. Still, it never states what a 'quota' record contains or what a caller should do with it, and the 'tenant' framing sits uneasily with a required region argument.

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% with a single required 'region' parameter, so the schema does the documenting and a baseline of 3 applies. The description adds no meaning beyond the schema; in fact the phrase 'for the tenant' is the only scoping information and it does not explain how 'region' narrows that scope.

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 pairs a specific verb ('List') with a specific resource ('DRS quotas') and a scope ('for the tenant'), so an agent can tell it apart from lifecycle siblings like hcloud_list_drs_jobs and hcloud_show_drs_job. It falls short of 5 because it does not distinguish itself from the other quota-reading tools in the fleet (hcloud_show_quota, hcloud_list_eip_quotas), whose scope overlaps conceptually.

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 guidance on when to call this tool versus alternatives, no prerequisites, and no note on what it is useful for (e.g. capacity planning before creating DRS jobs). The reader must infer the purpose from the name alone.

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