reset_sandbox

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It openly states the destructive action ('Destroy', 'clear all session state') and explains the consequence for future calls. This is transparent and leaves no ambiguity about the tool's side effects.

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 two sentences with no wasted words. It front-loads the core action and then adds the forward-looking consequence. Every clause contributes meaning, making it highly concise and well-structured.

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 zero-parameter, destructive reset tool with no output schema, the description fully covers what happens, the effect on session state, and the behavior of the next python_eval call. There is no missing information that would hinder correct invocation.

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 tool has zero parameters, so the baseline of 4 applies. The description adds no parameter-related information because none exists, which is appropriate. The relationship between the tool and the python_eval call is clear without needing parameter details.

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 specific verbs ('Destroy', 'clear') and identifies the exact resource ('Python sandbox container', 'session state'), making the tool's purpose unambiguous. It clearly distinguishes reset_sandbox from sibling tools like python_eval or upload_to_sandbox, as it is the only one performing a reset.

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 implies when to use the tool: when a fresh sandbox environment is needed, since it states 'The next python_eval call will create a fresh container.' It does not explicitly mention alternatives or exclusions, but no clear alternative exists among the sibling tools, so the contextual guidance is sufficient.

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