sandbox_kill

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

Clearly states destructive side effect: all data destroyed. No annotations provided, so description carries full burden; it does so completely.

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?

Two sentences, no filler, each sentence adds essential information: what it does and the consequence.

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?

Single parameter, no output schema required; description covers the action and irreversible nature fully. No gaps given tool simplicity.

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 provides 100% coverage for the single parameter 'sandboxId' with description stating 'The sandbox ID to terminate.' Description adds no extra meaning beyond the schema.

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?

Verb 'Terminate and clean up' clearly states action, resource is 'sandbox', and 'destroyed' emphasizes finality. Sibling tools like sandbox_pause or sandbox_keep_alive do not destroy the sandbox, making this unique.

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?

Explicitly states when to use: to terminate and clean up. It lacks explicit when-not-to-use or alternatives, but the uniqueness is clear from sibling names.

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