Checkpoint Delete

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is covered structurally. The description reinforces irreversibility with 'Permanently' and adds the exact-path constraint, but says nothing about permissions, whether deletion cascades, or recoverability.

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?

A single front-loaded sentence with no wasted words; the destructive nature and the path constraint both land immediately.

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 described, and the tool is a simple one-parameter mutation whose safety profile is carried by annotations. Only the path format and irreversibility details are thin.

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% for the single tinker_path parameter, so the description must compensate. 'At this exact Tinker path' implies exact matching (no globbing or prefix resolution), which is useful, but the expected path format is not explained.

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 ('Permanently delete the checkpoint') with the scoping qualifier 'at this exact Tinker path'. This distinguishes it from siblings like checkpoint_set_ttl or checkpoint_export, though it never names them explicitly.

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?

No guidance on when to use this versus checkpoint_set_ttl, checkpoint_unpublish, or other checkpoint lifecycle tools. The agent must infer the destructive-delete use case purely from the verb.

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