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

The description conveys the primary side effect (creating a snapshot) and its non-destructive nature, but does not clarify whether an existing checkpoint with the same name is overwritten or if any additional side effects occur. Annotations provide no further detail, so the description carries the burden but falls short on edge cases.

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—two sentences, front-loaded with the action and purpose. No extraneous words or 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?

Given the existence of an output schema (per context signals), the description covers the main intent, usage, and outcome sufficiently. It lacks explicit handling of name conflicts or failure modes, but these are not strictly required for a basic understanding. The description is complete enough for an agent to decide when and how to use it.

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 has zero descriptions for parameters. The description indirectly implies workflow_id ('current workflow') and name ('named checkpoint'), but the optional 'description' parameter is never mentioned. It does not fully compensate for the lack of schema documentation.

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 verb 'Snapshot' and the resource 'current workflow', and explains the purpose: creating a named checkpoint for later restoration. The added context about using it before risky edits reinforces the intent.

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 provides a usage scenario: 'Use before a risky batch of edits so you can roll back.' This tells the agent when to invoke the tool and distinguishes it from related tools like restore_checkpoint.

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