Create storage pool

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

Annotations already indicate destructiveHint=true, but the description adds specific context about potential data loss, which goes beyond the annotation. It also alerts the agent to require user confirmation. This adds behavioral transparency.

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?

Three concise sentences: purpose, risk warning, and action instruction. No wasted words, well-structured for quick comprehension.

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?

Given the tool's high complexity (24 params, no output schema, destructive), the description is too brief. It lacks prerequisite conditions, parameter dependencies, result expectations, and error handling. The risk warning is present but incomplete for safe usage.

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 24 parameters and only 13% schema description coverage, the description should clarify parameter usage but completely omits any parameter-level semantics. It relies solely on the sparse schema descriptions, which is insufficient for an agent to invoke correctly.

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 explicitly states 'Create a new storage pool' with types, but the vague 'etc.' and lack of precise definition of 'storage pool' in context slightly reduce clarity. It distinguishes from siblings like create_pool and other create_* tools.

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 includes a warning about high risk and instructs to ask user confirmation, which is helpful, but it does not provide guidance on when to use this tool vs. alternative creation tools, such as create_pool for HA pools.

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