create_system_shutdown

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

Annotations already indicate the operation is not read-only, is idempotent, and is not marked destructive, but the description adds no behavioral detail beyond the endpoint. It does not disclose that the action powers the system down, what side effects occur, or what the response represents; the misleading 'Create System.' line actively obscures the behavior.

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 short, but the opening sentence 'Create System.' is filler and misleading, while the genuinely useful endpoint is buried after a blank line. It should lead with the shutdown action and omit the rest.

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 zero parameters and an output schema, the tool is invocable from the endpoint alone, making this minimally viable. However, it lacks a plain statement of the operation's purpose and effects, so the agent must infer shutdown semantics from the URL.

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 has zero properties, so there are no parameter semantics for the description to clarify. Baseline 4 is appropriate because nothing is missing for invocation.

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 leads with 'Create System.' which is misleading and does not convey that this tool shuts down the system. The endpoint path 'POST /api/v3/system/shutdown' gives a technical hint, but the natural-language purpose is missing and it fails to distinguish the tool from create_system_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?

No guidance is provided about when to use this tool or when to prefer an alternative such as create_system_restart. The description only contains an endpoint, not situational context, prerequisites, or exclusions.

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