hcloud_list_eip_quotas

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is supplied structurally. The description adds nothing beyond them: no note that results are region-scoped, no indication of quota dimensions (used vs total), and no behavior for an unknown region. With annotations covering safety, the description still fails to contribute any extra operational context.

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 four-word phrase, front-loaded with the verb and resource and free of filler. Its brevity is efficient but edges toward under-specification rather than genuine conciseness.

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 one-parameter, read-only list tool with no output schema, a short description is defensible, but it omits the region scoping and the nature of the quota data returned. It is minimally sufficient rather than 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% but the single parameter is documented only as "Region" with no format hint. Per the high-coverage baseline this lands at 3, and the description does not compensate by naming expected region-code syntax or regional scoping behavior.

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 EIP resource quotas" names a specific verb (list) and resource (EIP quotas), which separates it from siblings such as hcloud_show_quota and hcloud_list_drs_quotas that deal with different quota scopes. It does not, however, spell out what an EIP quota represents or what the returned items look like.

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 use this tool versus hcloud_show_quota or other quota-listing tools, and no stated prerequisites beyond the required region. The agent must infer usage entirely from the name.

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