tenki_resume_sandbox

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

The annotations already signal that this is a non-read-only, non-destructive, non-idempotent operation, so the description does not need to restate that. The only additional behavioral context is the state precondition 'previously paused'; side effects such as billing, resource allocation, or failure modes are not disclosed.

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 a single, short sentence with no filler or redundant information. The key precondition, 'previously paused,' is stated directly and early, making it appropriately sized for a one-parameter state-transition tool.

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 tool with one fully documented parameter and annotations covering safety and mutation traits, the description provides the essential invocation condition. It does not describe return values or error behavior, but the operation can be selected and invoked correctly from the given text.

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 input schema already provides 100% parameter description coverage, including that session_id is a UUID from tenki_create_sandbox or tenki_list_sandboxes. The description adds no parameter-level detail, but the schema carries the burden sufficiently.

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 uses a specific verb, 'resume,' and identifies the resource, 'sandbox,' while adding the scope 'previously paused,' which separates it from create, pause, terminate, and list operations. It is unambiguous, though it does not explicitly name a sibling alternative.

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 phrase 'previously paused' implies that this tool is appropriate only for sandboxes currently in the paused state, which gives some usage direction. It does not explicitly state when not to use it or mention alternative tools like tenki_get_sandbox or tenki_pause_sandbox.

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