restart_sandbox

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

With no annotations, the description carries the full behavioral burden and supplies almost none. It does not disclose that restarting destroys running processes or in-memory state, whether it requires auth, or what happens to attached volumes/files — all critical for a potentially disruptive operation.

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 text is front-loaded and free of padding, which is a virtue, but the extreme brevity is under-specification rather than disciplined conciseness — the endpoint line adds little agent-facing value.

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 mutation tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. An agent cannot tell what state is lost on restart, whether it blocks, or what a successful response looks like.

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 single parameter 'name' has 0% schema description coverage, and the description only reveals it via the URL template '/sandboxes/{name}/restart'. It never states that this is the sandbox name, its format, or whether it must be unique/existing.

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 states a specific verb+resource ('Restart sandbox'), so the agent knows exactly what operation runs. However, it offers no differentiation from closely related siblings like wake_sandbox, keep_sandbox_awake, or deep_sleep_sandbox, so an agent must infer the semantic boundary itself.

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?

There is no guidance on when to use this tool versus sleep_sandbox, wake_sandbox, or keep_sandbox_awake, nor any stated prerequisites (e.g., sandbox must exist or be running). The HTTP line is a transport detail, not usage advice.

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