create_vzdump

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It mentions 'immediate backup' but does not address safety (e.g., whether it is destructive), required permissions, idempotency, or side effects like blocking during backup. This is insufficient.

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 brief summary followed by a clear parameter list. It is relatively concise, though the parameter list is somewhat lengthy. Every line contributes value, and the format is easy to scan.

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 (7 parameters) and existence of an output schema, the description covers parameter semantics adequately. However, it lacks operational context such as how the backup behaves (e.g., asynchronous), potential errors, or prerequisites like node readiness. This leaves gaps for an AI agent.

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?

Despite 0% schema description coverage, the description adds significant meaning to each parameter beyond the schema's defaults and types. For instance, it clarifies that vmid is comma-separated and conditionally required, and explains mode and compress options. This compensates well for the missing schema 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?

The description clearly states the tool's purpose: 'Start an immediate backup (vzdump) on a node.' It specifies the action (start), resource (backup), and context (node), distinguishing it from related tools like create_backup_job which handles scheduled backups.

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 some usage hints (e.g., vmid required if not all_guests) but fails to explicitly state when to use this tool versus alternatives like create_backup_job or backup-related operations. There is no direct guidance on prerequisites or exclusions.

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