list_k8s_clusters

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

Annotations already declare readOnlyHint=true, so read-only is known. The description adds context about default depth of 1 returning names and basic properties, and hints at nesting behavior. It does not contradict annotations and adds value beyond the read-only flag.

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?

Two concise sentences, no unnecessary words. The first sentence states purpose, the second explains default behavior. Perfectly front-loaded and efficient.

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 tool with one optional parameter and no output schema, the description is adequate. It explains scope and default behavior. It doesn't mention pagination or limits, but these are not critical for a basic list. The sibling get_k8s_cluster covers detailed properties, so overall completeness is good.

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 schema covers the depth parameter with a description (0-5, default 1), and the tool description reinforces that default returns basic properties. It adds meaning about how depth affects response, even though schema already documents the parameter well.

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 it lists all Kubernetes clusters in the IONOS Cloud account, differentiating from get_k8s_cluster (single cluster) and list_k8s_nodepools (nodepools instead). It explicitly mentions returning names and basic properties, giving a specific verb and resource.

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 for listing all clusters without explicit alternatives. It states 'all' which contrasts with get_k8s_cluster, but does not explicitly say when not to use or mention alternatives. However, the scope is clear enough for agent selection.

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