list_target_groups

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

The readOnlyHint annotation already discloses the safe read operation, and the description adds only the account scope. It does not describe return format, pagination, or performance, but this is not critical given the annotation. No contradiction is present.

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 description is a single, concise sentence that front-loads the core purpose. There is no redundant or tangential wording.

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 simple list operation with a read-only annotation and fully described parameters, the description is sufficient. It clearly states what it does and the scope. It could optionally mention the impact of filters or pagination, but these are already in the schema, so the description is complete enough for its simplicity.

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?

The input schema provides full descriptions for both depth and filters (100% coverage). The tool description adds no supplementary parameter semantics. The baseline of 3 is appropriate because the schema handles the burden, and the description does not enhance it.

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 clearly states the action (list), the resource (target groups), and the scope (all in the IONOS CLOUD account). It is unambiguous and distinct from siblings like get_target_group, which targets a single group.

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?

The description implies usage when you need all target groups, but it does not explicitly contrast with get_target_group or mention when not to use this tool. No alternatives or exclusions are provided, leaving some ambiguity for an agent choosing between list and get variants.

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