create_snapshot

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

Annotations only have openWorldHint: false. Description adds behavioral details: captures local variables at current frame, requires STOPPED state, and eviction policy. No contradiction.

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?

Five sentences, each adds essential information without redundancy. Front-loaded with purpose and key prerequisites.

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 simple tool with one parameter and no output schema, description covers purpose, prerequisites, capacity limit, and parameter semantics completely.

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' with no schema description. Description adds 'Unique name for this snapshot', specifying uniqueness constraint beyond basic type info.

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 states the action (capture), resource (local variables at current frame), and result (named snapshot). Clearly distinguishes from siblings like list_snapshots and diff_snapshots.

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 requires STOPPED state and breakpoint context, and mentions max snapshot capacity. Does not explicitly state when not to use or provide alternatives, but conditions are clear.

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