shutdown_devbox

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

No annotations are provided, so the description carries the full burden. It does disclose the destructive nature by saying 'delete' and 'release its resources,' which implies irreversible resource release. However, it does not explicitly warn about data loss, irreversibility, or consequences if the devbox is busy (though the force parameter is documented in the schema). The description offers basic transparency but lacks additional behavioral context like side effects or permissions.

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 a single sentence, front-loaded with the action, and contains no redundant information. It efficiently conveys the primary purpose and the fact that resources are released.

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?

The tool is simple with two well-documented parameters and an output schema, so the description doesn't need to explain return values. However, the description is minimal and lacks usage context or warnings about irreversibility. It is adequate for basic understanding but not fully complete for a destructive operation without annotations.

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 input schema provides 100% coverage for both parameters (devbox_id and force), each with clear descriptions. The tool description adds no additional meaning about parameters, such as when to set force or the effects of the default value. Schema coverage is high, so the baseline of 3 is appropriate.

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 clearly states the tool's function: 'Shut down (delete) a devbox and release its resources.' It specifies the verb (shut down/delete) and resource (devbox), and the parenthetical 'delete' distinguishes it from sibling suspend_devbox, which likely pauses rather than removes the devbox.

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 provides no explicit guidance on when to use this tool versus alternatives like suspend_devbox or resume_devbox. While 'delete' implies permanent removal, it does not directly state that this is for final decommissioning or that suspend should be used for temporary pauses. There is no context or exclusion criteria.

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