cloud_shutdown_server

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

The description discloses that it is an ACPI graceful shutdown, but with no annotations, it lacks details on return format, error handling, or side effects beyond the basic action.

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 extremely concise (one phrase), which aids quick scanning, but it could be slightly more structured with a complete 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?

Given the output schema exists, the description doesn't need to explain returns, but it lacks information on whether the operation is asynchronous or the expected action result.

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 description does not add any meaning to the single parameter 'server_id'. Schema coverage is 0%, and the description does not explain what server_id refers to or its format.

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 verb 'shutdown', the resource 'cloud server', and the method 'ACPI (graceful)', which distinguishes it from sibling tools like cloud_power_off_server (hard power off) and cloud_reboot_server (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 implies graceful shutdown but does not explicitly state when to use this tool over alternatives like cloud_power_off_server or cloud_reboot_server, nor does it mention prerequisites (e.g., server must be running).

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