diagram_snapshot

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

There are no annotations, so the description carries the burden of behavioral disclosure. It usefully states that snapshots live under the user data directory and not the agent cwd, but it does not disclose whether reusing the same label overwrites an existing snapshot or creates a duplicate, nor what the tool returns.

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, tightly worded sentence that front-loads the action and immediately states the critical location constraint. Every element earns its place with no filler.

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 one-parameter, read-like snapshot operation, the description is largely complete for correct invocation: action, destination, and labeling are covered. The only substantive gap is duplicate-label behavior, which would strengthen the description further but is not essential for a first call.

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 fully documents the single parameter 'label' with a helpful example, so the schema covers the semantics. The tool description adds no additional meaning beyond the schema, keeping this at the baseline score for full schema coverage.

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 identifies the verb ('Copy'), the resource ('current diagram'), and the destination ('a labeled snapshot under the user data directory'). The explicit parenthetical 'not the agent cwd' prevents a common mistake and helps distinguish this from file-exporting siblings like diagram_export.

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 snapshot concept implies a checkpointing use case, but the description does not explicitly say when to prefer this over diagram_restore, diagram_export, or diagram_patch. It provides useful context about where the snapshot is stored, but no explicit when-to-use or when-not-to-use guidance.

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