boxes.shutdown

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

With no annotations, the description bears full burden. It explains the default graceful shutdown and the force option for immediate destruction, but omits details such as authentication needs, rate limits, resource state transitions, or confirmation prompts. Basic behavioral traits are disclosed, but more context is expected.

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, efficient sentence that front-loads the core action and default behavior. Every word is informative, with no redundancy or unnecessary details.

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 relatively simple tool with two parameters and no output schema, the description covers the main behavioral aspects (default graceful, force option). It is missing some context around post-shutdown state and differentiation from suspend/reboot, but overall adequate.

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 100% with clear parameter descriptions. The description adds only the context of 'graceful by default' and implies the force parameter's effect, but does not introduce new meaning beyond the schema. 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 action ('Shutdown/Power off') and the resource ('a domain'), with a qualifying note about default gracefulness. This distinguishes it from sibling tools like boxes.reboot (restart) and boxes.suspend (pause), providing clear purpose.

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 powering off a domain but does not explicitly state when to prefer this over alternatives like boxes.reboot or boxes.undefine. There is no mention of when not to use, prerequisites, or preconditions.

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