ncloud_dataforest_kill_container

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

Annotations indicate destructiveHint=true and idempotentHint=true. The description merely says 'Restart', adding no additional context about side effects, state changes, or required states. It does not contradict annotations but fails to expand upon them.

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 sentence, which is concise, but the choice of 'Restart' instead of 'Kill' misaligns with the tool name, reducing clarity. The sentence is front-loaded but could be more accurate.

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 tool has no output schema and only two parameters, the description lacks details on prerequisites (e.g., app must be running), return values, or error conditions. For a destructive operation, more context is needed for safe agent usage.

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 covers both parameters with descriptions (id as Base62-encoded UUID, containerName with examples). Schema description coverage is 100%, so the description adds no further meaning beyond what the schema already provides. Baseline score 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 verb 'Restart' and the resource 'specific container in a Data Forest app component', which is specific and differentiates it from sibling tools like ncloud_dataforest_kill_master. However, the tool name 'kill_container' contradicts the described action, causing potential confusion.

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 no guidance on when to use this tool versus alternatives such as ncloud_dataforest_start_app, ncloud_dataforest_stop_app, or ncloud_dataforest_kill_master. No conditions, prerequisites, or exclusions are mentioned.

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