shutdown

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

Annotations already indicate destructiveHint: true, so the destructive nature is known. The description adds a behavioral guard: 'Requires confirm=True.' This is beyond the annotation and informs the agent that confirmation is mandatory, providing useful extra transparency about how the tool behaves.

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 short sentences, front-loaded with the primary action. It contains no filler or redundant repetition of the tool name, and every word adds value. This is an example of efficient, well-structured writing.

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 simple tool with one parameter, no output schema, and a destructive annotation, the description covers the essential action and the critical confirmation requirement. It is complete enough for an agent to select and invoke the tool safely.

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 description coverage is 0%, but the description directly addresses the single parameter: 'Requires confirm=True.' This clarifies the meaning and importance of the 'confirm' boolean, which is otherwise only shown in the schema with a default. This compensates for the lack of schema documentation.

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 states exactly what the tool does: 'Power off the NAS.' This uses a specific verb ('Power off') and a clear resource ('the NAS'), and it distinguishes the tool from siblings like 'reboot' and 'restart_stack' by indicating a full shutdown rather than a restart.

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 a clear usage condition: 'Requires confirm=True.' This tells the agent that the tool will not execute without explicit confirmation, which is a key usage guideline. It does not explicitly discuss when to use vs. alternatives, but for a shutdown tool with few similar siblings, this is adequate context.

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