Preview deleting a project document

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

The description explicitly states the tool itself modifies nothing, aligning with the readOnlyHint annotation. It details the reference scan and checkpoint commit behavior, adding significant context beyond annotations.

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?

The description is detailed but not overly long; it front-loads the purpose. However, the technical details on reference scan types could be slightly more concise.

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?

The description covers the tool's non-destructive nature, the reference scan preconditions, and the checkpoint mechanism, providing a complete behavioral picture given the annotations and output schema.

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 single 'path' parameter has full schema coverage, and the description adds clarity by specifying it must be a canonical project-relative POSIX path, reinforcing the schema's constraints.

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 clearly states the tool's function: planning permanent deletion of a TMJ map or TSJ tileset. It uses a specific verb and resource, distinguishing it from sibling tools that deal with checkpoints, rendering, or other operations.

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 implies when to use (for planning deletion of a single project-local file) but does not explicitly mention when not to use or provide alternative tools. The reference scan details give context, but no direct comparison to siblings.

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