Create Snapshot

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds substantial behavior: leading-DTG replacement, collision handling via numeric suffix, no source modification, and no auto-pruning. No contradiction with 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?

Every sentence carries a distinct piece of information: naming, permanence, prune behavior, collision behavior, non-modification, and usage timing. The most important format detail is front-loaded.

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?

Covers naming, collision, retention, source safety, and a concrete usage trigger; an output schema exists so return values need no explanation. The only material omission is the meaning and effect of 'dest_dir', which prevents a perfect completeness score.

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%, and the description adds useful meaning for 'label' (optional short label) and file_path (the unmodified source), plus the naming convention. However, 'dest_dir' is never explained, leaving one of three parameters under-specified.

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 ('Save') and resource (a DTG-stamped permanent copy with a precise naming format), and clearly distinguishes snapshots from automatic prev/anchor slots and manage_backups. This is far more informative than the title alone.

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?

Explicitly says to take a snapshot before any large or risky editing pass and explains that snapshots are permanent keepers whereas automatic slots rotate. It mentions manage_backups does not touch snapshots, but does not fully spell out when to choose snapshots over that sibling tool.

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