create_storage

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

No annotations are present, so the description carries the full burden. While it implies mutation by saying 'Create,' it fails to disclose behavioral traits such as whether the operation is destructive, requires specific permissions, or has side effects. The agent gets no warning about potential impacts.

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 structured as a clear list of parameter explanations following a concise opening sentence. While lengthy due to the number of parameters, it avoids unnecessary verbosity and is easy to parse. The first sentence effectively sets the 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?

Given the tool's complexity (17 parameters) and the presence of an output schema, the description adequately covers parameter semantics but misses behavioral context like error conditions, prerequisites, or output expectations. It meets the minimum viability but has 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?

The input schema has 0% description coverage, but the description provides brief explanations for all 17 parameters (e.g., 'Storage ID', 'Storage type', 'File system path'), adding substantial meaning beyond titles and defaults. This compensates well for the schema's lack of descriptions.

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?

Description states 'Create a new storage pool configuration,' which is a specific verb and resource. However, it does not differentiate from numerous sibling tools like create_lvm, create_lvmthin, create_directory_storage, etc., which also create storage configurations. The agent cannot easily determine when to use this generic tool versus the specific ones.

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?

No guidance is provided on when to use this tool versus alternatives. The description merely lists parameters without explaining prerequisites or contextual usage. The agent has to infer from the parameter list alone.

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