sandbox_pause

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

No annotations are provided, but the description discloses key behaviors: sandbox persists across sessions, does not count against timeout, and can be resumed. This goes beyond a simple 'pause' verb, giving the agent important operational details. However, it doesn't mention if there are costs or limits on paused sandboxes.

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?

Three sentences, no wasted words. Front-loaded with the core action and followed by clarifying details. Perfectly concise.

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?

The description covers purpose, effect, and relationship to resume. Given the simple tool (single parameter, no output schema), it is complete enough. It could mention persistence or cost implications, but not essential for basic usage.

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% with one required parameter 'sandboxId' described simply as 'The sandbox ID to pause.' The description adds no additional semantics beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states the action ('Pause a sandbox') and the resource ('sandbox'). It distinguishes from siblings by mentioning that it preserves state and can be resumed later with sandbox_resume, differentiating it from sandbox_kill which would destroy the sandbox.

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 provides clear usage context: pausing preserves state for later resumption. It mentions the alternative (sandbox_resume) but doesn't explicitly state when not to use this tool (e.g., vs sandbox_kill). However, the context implies it's for temporary halts.

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