snapshot_save

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

No annotations are present. The description discloses that a named snapshot is created, but it does not mention overwrite behavior, persistence, or whether the current Edit remains unchanged. Adequate but not detailed.

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?

One concise sentence with no filler. The verb and object are front-loaded, making the tool's core function immediately clear.

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?

Given the simple schema and the presence of sibling tools like snapshot_recall and snapshot_list, the description gives enough context for typical use. Minor gaps remain around name conflicts, overwrite behavior, and snapshot scope.

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 schema lists 'name' as a required string, and the description ties it to naming the snapshot, but it does not add constraints, format rules, uniqueness expectations, or examples beyond the schema.

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?

Clearly states the action (save), the object (current Edit as a named snapshot), and the purpose (later A/B compare or recall). It is also distinguishable from regular edit_save by the snapshot concept.

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?

Provides some context for intended use ('later A/B compare or recall') but does not explicitly contrast with edit_save or state when snapshot_save should be preferred over a regular save. No alternative guidance is given.

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