instance_shutdown

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

Goes beyond the annotations by explaining the mechanism: an ACPI event is sent for the guest OS to perform a clean shutdown, which tells the agent this is graceful rather than an immediate power cut. It omits whether the call is asynchronous, what happens if the guest ignores ACPI, or what is returned.

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 compact sentences, front-loaded with the action and identifier, then the behavioral explanation. The only flaw is a minor restatement of the tool name in the second sentence.

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?

Adequate for a simple single-parameter mutation with no output schema, but it leaves out async/completion semantics and any contrast with instance_stop or instance_restart, which are the main decision points for an agent.

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%, so both parameters are already documented; the description only restates 'by its id'. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb+resource ('Shutdown compute instance / resource by its id') and includes the endpoint. However, it never distinguishes itself from the close sibling instance_stop, which an agent must choose between.

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 power-button analogy and 'ACPI event ... clean shutdown' imply graceful shutdown, hinting at when this is preferable to a hard stop, but no alternative is named and no exclusion condition is given. Usage is inferred rather than stated.

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