pve_create_container_snapshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. It doesn't mention whether this is a destructive operation, what permissions are required, whether it affects container availability during snapshot creation, what happens if a snapshot with the same name exists, or what the expected outcome looks like. For a mutation tool with zero annotation coverage, this is critically inadequate.

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?

While technically concise with just three words, this description suffers from severe under-specification rather than effective brevity. The single phrase doesn't earn its place by providing meaningful guidance or context. True conciseness balances brevity with completeness, which this description fails to achieve.

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?

For a mutation tool that creates snapshots with 4 parameters and no annotations or output schema, the description is completely inadequate. It provides no behavioral context, no usage guidance, no error handling information, and no indication of what the tool returns. The agent would struggle to use this tool correctly based solely on this description.

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 schema description coverage is 100%, with all parameters clearly documented in the input schema. The description adds no additional parameter information beyond what's already in the structured schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Create container snapshot' is a tautology that essentially restates the tool name 'pve_create_container_snapshot' without adding meaningful context. While it identifies the verb ('create') and resource ('container snapshot'), it lacks specificity about what this operation entails and doesn't differentiate from sibling tools like 'pve_create_vm_snapshot' or 'pve_list_container_snapshots'.

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 absolutely no guidance about when to use this tool versus alternatives. There's no mention of prerequisites, appropriate contexts, or comparisons to related tools like 'pve_rollback_container_snapshot' or 'pve_delete_container_snapshot'. The agent receives no help in determining when this specific snapshot creation tool should be selected.

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