wipe_lab

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

Discloses key behavioral traits: startup configuration via set_node_config is preserved, runtime/learned state is discarded, and the lab must be stopped. The destructive nature is implicit in 'wipe' but explicitly scoped. Does not address the wait parameter's role in execution timing.

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: the first states the core action concisely, the second adds essential preservation and prerequisite details. No redundant or filler language.

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?

Covers the main functional aspects of a destructive reset: scope (every node), what is preserved, what is discarded, and the prerequisite. Missing explanation of the wait parameter and potential async behavior, but output schema exists and overall guidance is strong.

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 0%, so the description must compensate, but it does not explain the purpose of the 'wait' parameter. 'lab_id' is self-evident, but 'wait' remains ambiguous. The description adds minimal parameter-level 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?

The description uses a specific action ('wipe') and resource ('every node's disks'), clearly indicating a lab-level reset operation. It distinguishes itself from sibling tools by focusing on disk wipe rather than configuration changes or node operations.

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 a prerequisite: 'The lab must be stopped first', giving clear context for when to use. However, it does not mention alternatives or situations where one should not use this tool, so it stops short of full guidelines.

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