Manage Snapshots

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

The annotations indicate destructiveHint=false, yet the description includes 'revert' and 'undo' actions which are destructive operations. This is a clear contradiction. Additionally, the description does not disclose side effects like state mutation, permission requirements, or irreversible changes, so behavioral transparency is severely lacking.

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 concise, a single sentence that enumerates the supported actions. It is well-structured and front-loaded with the overall purpose, making it easy to scan and understand.

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?

The description omits crucial context: it does not mention what each action returns, whether results are paginated, error handling, or examples. Since there is no output schema, the description should clarify expected outputs but does not. It also lacks notes on side effects or limitations, leaving an agent with incomplete information for invoking the tool correctly.

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 descriptions cover all 9 parameters, but the tool description itself does not elaborate on parameter usage. It does list the action values in the text, which partially clarifies the action parameter, but it does not map parameters to specific actions or explain how they interact. The description adds some value by naming the actions, but parameter semantics are mostly derived from 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?

The description clearly states the tool manages snapshots and lists the specific actions (save, list, diff, get_state, revert, undo, get_history). This distinguishes it from sibling tools like manage_nodes or query_graph, so an agent can identify its purpose readily.

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 description provides no guidance on when to use this tool vs alternatives. It does not mention conditions like 'when you need to save or revert state' or reference scenarios that would make this tool preferable to others. The action list is informative but lacks situational context.

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