pve_storage_create

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

Without annotations, the description carries the full burden. It labels the tool as 'MUTATION' and explains the dry-run/confirm pattern, which is key for safe usage. However, it does not disclose potential side effects, permissions required, or what happens after creation.

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 two sentences long and front-loads the purpose. Every word is necessary and contributes to understanding, with no wasted text.

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 (11 parameters, required fields, output schema), the description is too minimal. It lacks context about storage types, parameter relationships, and any constraints, making it incomplete for an agent to use effectively.

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 only 9% schema description coverage (only one parameter described), the tool description adds no parameter information beyond names. For a tool with 11 parameters, this is insufficient to guide correct parameter usage.

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 'define a new storage (storage.cfg)', specifying the verb 'define' and the resource 'storage', which unambiguously indicates the tool's purpose among siblings like pve_storage_delete and pve_storage_update.

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 explicit usage guidance by stating 'Dry-run by default. confirm=True to execute.' This tells the agent when to use the tool and how to ensure execution, though it does not discuss prerequisites or alternatives.

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