save_snapshot

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

No annotations provided; description discloses that geometry is saved and namespace is not. However, does not mention side effects, limits, or behavior beyond saving. Adequate but not thorough.

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: first states purpose and scope, second provides usage guideline. No filler, front-loaded information.

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 simple tool with one parameter and existing output schema, the description covers purpose, scope, and usage context completely. Sufficient for agent decision-making.

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?

Single parameter 'name' is described as 'named checkpoint' but no specifics on format, constraints, or conventions. Schema coverage is 0%, so description adds only minimal context.

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 named checkpoint of geometric state (current_shape and show() registry). It specifies what is saved and what is not (Python variable namespace). Distinguishes from sibling restore_snapshot.

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 calling before risky experiments to restore known-good geometry without re-running execute() calls. Provides clear context but does not contrast with alternatives.

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