Export Snapshot Archive

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

Annotations already cover the safe read-only/idempotent nature, and the description adds valuable behavioral context about the output format (a standalone JSON archive with states, transitions, and metadata). However, it does not address error cases or size limitations.

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 a single, well-structured sentence that front-loads the verb and resource, with no filler or unnecessary detail.

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 simple tool with one parameter and good annotations, the description explains the essential purpose and output content. It could additionally mention behavior for nonexistent snapshots, but the current description is sufficiently complete for a basic export operation.

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 coverage is 100%, including a clear description of the 'name' parameter. The description's use of 'named' adds no new meaning beyond the schema, so it does not go above the baseline for well-documented schemas.

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 action ('Export'), the resource ('a named visual snapshot'), and the resulting output ('a full standalone JSON archive containing states, transitions, and metadata'). This distinguishes it from sibling tools like diff_visual_snapshots and export_visual_trajectories.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description implies exporting for external use, but it does not mention when to prefer it over restore_snapshot or export_visual_trajectories.

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