checkpoint

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

Annotations declare readOnlyHint=false and destructiveHint=false, yet the description lists 'delete' and 'prune' operations, which inherently remove data, and 'restore', which can overwrite project state. The description does not clarify this tension, nor does it say what a checkpoint contains, whether restore is reversible, or what compare returns. It adds essentially nothing beyond the operation names already in the enum.

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, purpose front-loaded and the operation list compactly encoded. No filler or redundancy.

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 six-parameter multi-operation tool with no output schema, the description is too thin: it never explains what a checkpoint is, what restore/prune actually do to project state, or how compare differs from a diff. Annotations only cover the safety profile, so the behavioral burden falls on the description and is largely unmet.

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 100%, and the schema already documents each parameter's role and defaults (e.g., keep_last default 10, checkpoint_id for restore/delete/compare). The description repeats the operation set but adds no syntax, format, or interaction detail beyond the structured fields, so baseline 3 applies.

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+resource ('Unified checkpoint CRUD') and enumerates the six operations, so the agent immediately knows the domain. It is clear and self-contained, but it does not distinguish itself from any sibling tool or clarify scope beyond the name.

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 op enum and the '(default)' marker imply usage, and listing the operations gives a rough map of when each branch applies. However, there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives among the many sibling tools.

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