hcloud_list_placement_groups

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that, and 'Returns all Placement Group objects' is mildly misleading given the schema exposes name/type/label_selector filtering and pagination.

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?

Very short and front-loaded, but the second sentence is pure restatement rather than adding information, so the brevity reflects under-specification rather than tight editing.

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 7-parameter, paginated list tool with no output schema and default auto-pagination, the description says nothing about return shape, pagination behavior, or filtering, leaving real gaps despite rich annotation coverage on safety.

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 seven parameters (name, page, sort, type, per_page, auto_paginate, label_selector) are already documented in the schema. The description adds no extra meaning, which meets the baseline when the schema does the heavy lifting.

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?

States a verb+resource (list Placement Groups) plus a redundant restatement ('Returns all Placement Group objects'). It does not distinguish the tool from the sibling hcloud_get_placement_group (single fetch) or from the other hcloud_list_* tools beyond the resource name.

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?

No guidance on when to use this versus hcloud_get_placement_group or the many related list tools; no mention of filtering, pagination, or prerequisites. The agent must infer everything from the name and schema.

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