save_snapshot

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

No annotations provided, so description carries full burden. It discloses what is saved (geometry) and what is not (namespace), and states the benefit of restoring known-good geometry without re-executing. No contradictions.

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 concise sentences, each packed with essential information. No wasted words. Front-loaded with the core action and scope.

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?

Covers key aspects: what is saved, when to use, and parameter meaning. Does not mention behavior on duplicate names or error scenarios, but given simplicity and output schema existence, it is nearly complete.

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?

Only one parameter 'name'. Description adds meaning by labeling it as a 'named checkpoint', but lacks details like uniqueness constraints or naming conventions. With 0% schema coverage, it compensates adequately but not fully.

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 it saves a named checkpoint of geometric state, including current_shape and show() object registry. It explicitly distinguishes what is saved (geometry) and what is not (Python variable namespace), providing high specificity.

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 when to use it ('before risky experiments') and contrasts with the alternative of re-running execute() calls. Implies usage of restore_snapshot later, offering clear context and alternative.

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