destroy_machine

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

With no annotations, the description carries the full burden. It discloses the idempotent nature (double-destroy is common), the non-error return for unrecognized session IDs, and the side effect of releasing the subprocess. It does not detail permission requirements or other side effects, but for a simple teardown tool, this is sufficient.

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, front-loaded with the primary action, and includes only essential behavioral detail. It is 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 single-parameter destruction tool with an output schema, the description adequately covers the purpose, the main error case, and the idempotency caveat. It does not describe success return or cleanup details, but these are likely covered by the output schema. Overall, it is complete enough for an agent to safely invoke.

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 schema has 0% description coverage, so the description must compensate. It references 'session id' in the return text, confirming that the parameter is a session identifier, but it does not explain where the ID comes from (e.g., create_machine) or its format. This adds minimal value beyond the schema's title.

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 ('tear down', 'release') and identifies the resource ('session', 'beebjit subprocess'). It clearly distinguishes from sibling tools like create_machine and reset by describing termination rather than creation or state 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 usage for ending a session but does not explicitly state when to use it vs. alternatives. The double-destroy note gives contextual guidance that calling it on an unrecognized session is safe, but no direct comparison to reset or other lifecycle tools is provided.

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