save_snapshot

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

With no annotations, description carries full burden. 'Deep-copy' indicates non-destructive, and 'Use before irreversible actions' implies safety. However, it doesn't mention performance, storage impact, or concurrency behavior. Adequate but not rich.

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?

Two sentences, front-loaded, no extraneous content. Efficient and scannable.

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 snapshot save with one param and no output schema, description covers core purpose and usage. However, missing parameter explanation leaves a gap that undermines completeness.

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?

Input schema has one required 'label' parameter with zero documentation. Description fails to explain its purpose (e.g., identifier for later restoration). Schema coverage is 0%, so description must compensate but does not.

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?

Description clearly states the tool saves a deep-copy snapshot of OMS and session state, with a specific verb-resource combination. It distinguishes from siblings like rollback_to_snapshot (restore), list_snapshots (list), and diff_snapshot (compare).

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 advises use before irreversible actions, providing clear context for when to use. No explicit exclusions, but the implication is strong. Better than average but lacks comprehensive guidance.

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