hcloud_show_image_quotas

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, and the description adds nothing on top of that. It says nothing about whether quotas are per-region limits vs. current usage, whether missing regions error out, or what a quota response contains. For a near-empty description against annotations, this is below the added-value bar.

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 phrase is front-loaded and free of waste, so it is structurally clean. But brevity here comes from under-specification rather than economy — there is only one clause and no useful content follows it.

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?

With no output schema, the description is the only place that could explain what quota data comes back (limit/used/reserved fields, per-region behavior), and it does not. The one required parameter is documented by the schema, but the agent still cannot predict the response shape or the region's role.

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?

There is one required parameter (region) with 100% schema description coverage, so the schema carries the documentation load. The description adds no meaning about what region scoping does (e.g., whether quotas differ per region or whether an empty result is possible), so baseline 3 applies.

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?

"Show IMS image resource quotas" identifies the resource (IMS image quotas) and the read action, which is marginally more specific than the name alone. However, it does not distinguish this from other quota-listing siblings such as hcloud_show_quota, hcloud_list_drs_quotas, or hcloud_list_eip_quotas, nor does it clarify what an "IMS image quota" covers.

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 or when-not-to-use guidance at all. The description never mentions the alternative quota tools or the image tools (hcloud_list_images, hcloud_show_image), leaving the agent to infer selection purely from the tool name.

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