hmc_remove_memory_pool

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

The description goes far beyond the destructiveHint annotation. It details the pre-flight check (fetches pool list, verifies existence, checks LPAR assignments), the exact command executed, the UUID-to-CLI-name resolution with fallback, the immediate return (no job polling), and the error raise conditions. This is extensive behavioral disclosure.

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 multi-paragraph but well-structured: purpose, preconditions, command, resolution, warning/returns, and errors. Every sentence earns its place given the destructive nature and need for safety. It's slightly longer than strictly necessary but not bloated.

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 description is comprehensive for a two-parameter destructive tool: it explains what it does, when it fails, what it returns, and how it resolves input. The output schema exists and the description covers the return value sufficiently. No major gaps.

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?

With 0% schema description coverage, the description fully compensates. It explains that system_name_or_uuid can be a CLI name or UUID (with resolution behavior) and that pool_name must refer to an existing pool with no assigned LPARs. This adds crucial meaning beyond the bare schema.

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 a specific action: 'Remove a shared memory pool from a managed system via the HMC CLI.' This distinguishes it from siblings like hmc_list_memory_pools and other management tools. The verb-resource pair is unambiguous.

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 provides strong context: it explains the preconditions (pool exists, no LPARs assigned), warns about permanence, and notes when the command will not execute. However, it does not explicitly name alternative tools for listing pools or explicitly state when-not-to-use scenarios beyond the safety checks.

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