delete_checkpoint

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

No annotations are provided, so the description carries the full burden. For a destructive delete operation it discloses nothing about irreversibility, whether restore_checkpoint can undo it, permissions, or error behavior when the name is ambiguous or missing.

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?

Front-loaded with the action, followed by a compact Args block that adds only what is needed. No wasted prose; slightly mechanical but efficiently structured.

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 not be explained. However, for a destructive tool with zero annotation coverage, the description should at minimum flag destructive/irreversible behavior, which it omits entirely.

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 0%, so the description must compensate, and it does: it explains that 'name' is a checkpoint name from list_checkpoints or an unambiguous prefix, adding real semantics absent from the bare string-typed schema property.

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: delete one recorded environment state. It is clearly distinguishable from create_checkpoint and restore_checkpoint in the sibling list, though it does not explicitly name an alternative or contrast with restore_checkpoint.

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?

Implied usage only. The description tells the agent the name must come from list_checkpoints or be an unambiguous prefix, which is useful procedural context, but it never states when to delete versus restore a checkpoint, nor whether this is reversible.

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