hmc_list_clusters

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

The read-only nature is already declared via readOnlyHint=true, and the description adds the useful context that clusters are sets of VIOS nodes sharing a storage pool. However, no additional behavioral traits such as return format, pagination, or filtering behavior are disclosed.

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, front-loaded sentence: 'List Clusters (sets of VIOS nodes sharing a storage pool).' It contains no unnecessary words and immediately conveys the tool's purpose.

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 zero parameters, a read-only annotation, and an output schema present, the description is fully adequate. It defines the key term 'clusters,' which is the only contextual information needed for this simple listing tool.

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 has zero parameters, so the baseline for parameter semantics is 4. The description does not need to document parameters, and its clarification of what a cluster is adds context to the result set without being parameter-related.

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 uses a specific verb ('List') and resource ('Clusters'), and defines clusters as 'sets of VIOS nodes sharing a storage pool.' This clarifies the tool's scope and distinguishes it from related siblings like hmc_shared_storage_pools and hmc_vios.

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 the tool is used for listing clusters, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. There is no mention of related tools or conditions that would favor this one, so usage guidance is only implied.

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