tenki_pause_sandbox

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

Annotations already indicate this is a non-read-only, non-destructive operation. The description adds specific behavioral detail by stating that it snapshots and suspends the sandbox, making the state change understandable. It does not mention side effects like billing or process behavior, but the disclosed snapshot+suspend behavior is meaningful and not contradicted by the annotations.

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?

A single, compact sentence that front-loads the action and resource, then explains the mechanism and lifecycle intent. There is no wasted wording or redundancy.

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?

For a simple one-parameter lifecycle tool, the description plus schema and annotations cover what the agent needs: what the tool does, that it is non-destructive, and where to obtain the session_id. No output schema exists, and the description adequately conveys the relevant state change.

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?

Schema coverage is 100%, so the session_id parameter is already well documented in the schema, including its source from tenki_create_sandbox or tenki_list_sandboxes. The tool description itself does not add parameter-level guidance, but it does not need to because the schema already carries that weight.

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 names a specific verb ('Pause'), a specific resource ('sandbox'), and the concrete mechanism ('snapshot + suspend'). It also conveys the lifecycle intent ('so it can be resumed later'), which clearly distinguishes it from terminate, resume, or standalone snapshot tools.

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 gives clear context: use this when you want to temporarily suspend a sandbox while preserving its state for later resumption. It does not explicitly name alternatives or exclusions, but the intent is clear enough that an agent can select this over terminate_sandbox or create_snapshot.

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