hcloud_show_quota

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 covered. The description adds almost nothing beyond restating the resource: it does not say whether quotas are returned as absolute limits, used/available counts, or per-project versus per-region scope, nor what a caller learns from the result.

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?

It is a single front-loaded phrase with no filler, so nothing is wasted. The problem is under-specification rather than verbosity; the same brevity with a clarifying clause about what quota data is returned would cost 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?

The tool is simple (one required parameter, no output schema), so the description carries responsibility for explaining what comes back, and it does not. An agent cannot tell what a quota response contains or how it relates to siblings like hcloud_show_server_limits and hcloud_list_eip_quotas.

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 coverage is 100%, so the single region parameter is documented in the schema (albeit minimally as just "Region"). The description adds no format hints, allowed values, or default, so the baseline of 3 applies rather than anything higher.

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 names a verb ("Show") and a resource ("VPC resource quotas"), but it is a bare noun phrase with no scope detail. It does not distinguish this from other quota tools in the sibling list such as hcloud_list_eip_quotas, hcloud_list_drs_quotas, or hcloud_show_image_quotas, so an agent cannot tell which quota family to pick from the name and text alone.

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 precondition for the required region argument, and no mention of alternatives. The agent must infer entirely from the tool name that this answers "how much VPC capacity is left in a region" rather than listing VPC objects.

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