pve_pool_create

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

With no annotations, the description informs that it is a mutation, defaults to a dry-run plan, is synchronous, and typically returns null. This adds behavioral context beyond the schema. Could mention error scenarios or permissions but covers main traits.

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 sentences with front-loaded action and key details. Each sentence contributes useful information. Could be slightly more concise but no redundancy.

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 presence of output schema and 100% schema coverage, the description adequately covers primary behavior, dry-run plan, execution, and post-creation steps. Missing details like error handling or permissions, but still complete for typical use.

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?

Schema coverage is 100%, but the description adds value by explaining the dry-run behavior linked to the confirm parameter and the asynchronous step of adding members via update. This clarifies the semantics beyond the schema definitions.

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 'MUTATION: create an (empty) resource pool', providing a clear verb and object. It distinguishes itself from sibling tools like pve_pool_update by noting it creates an empty pool and that adding members is done via 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?

It explains the dry-run default behavior and the need for confirm=True to execute. It also references pve_pool_update for adding guests/storage, offering alternatives. However, it does not explicitly state when not to use the tool.

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