get_vzdump_extractconfig

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

Description states 'extract' implying a read operation, but does not explicitly declare no side effects or permissions needed. With no annotations, the description should provide more behavioral context (e.g., read-only, required privileges).

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 brief and to the point. The first sentence states the purpose, and the Args are clearly formatted. No redundant information.

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 an output schema, the description does not need to explain return values. However, it lacks context on error conditions, permissions, and edge cases. The tool is simple but the description leaves 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 description provides explanations for both parameters, supplementing the schema which lacked descriptions. It includes an example for the volume parameter, clarifying the expected format. This adds value beyond the schema.

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 specifies the action 'extract' and the resource 'guest configuration from a vzdump backup archive'. Among siblings, it is unique as it deals with extracting config from backup archives, distinct from other get_* tools that retrieve live configs.

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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or exclusions. The agent must infer usage from context.

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