checkpoint_create

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the mutation risk profile is covered structurally. The description adds the authorization gating context, but says nothing about resource cost, what a checkpoint consumes on the host, or whether repeated calls with the same name collide.

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?

Two short sentences with the action front-loaded ahead of the precondition. The second sentence is terse to the point of using unexplained internal flag names, but nothing is wasted.

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?

An output schema exists, so return values need no explanation, but the definition leaves the two required parameters completely undocumented and refers to 'ALLOW_CHECKPOINTS' and 'an allowlist' without saying how they are satisfied. For a destructive write tool with zero schema coverage, that is a meaningful gap.

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 description coverage is 0% for both required parameters, so the description must carry the meaning of vm_name and name but mentions neither. An agent must infer that vm_name selects the target VM and name labels the checkpoint, with no guidance on naming rules or uniqueness.

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?

States a specific verb and resource ('Create a manual checkpoint'), which distinguishes it from checkpoint_list, checkpoint_restore and checkpoint_delete by name. It does not explicitly explain how 'manual' differs from an automatic checkpoint, so it falls short of full sibling differentiation.

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?

Names two preconditions (ALLOW_CHECKPOINTS and an allowlist) that must hold before calling, which is a real usage gate. However, it never says when to choose this over checkpoint_restore/delete or what to do if the gate fails, and neither flag is explained.

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