ncloud_dataforest_kill_master

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

Annotations provide destructiveHint=true and idempotentHint=true, but the description adds no behavioral details beyond 'Restart'. The name 'kill_master' contradicts the restart action, causing confusion about the tool's true effect. No disclosure of side effects, such as downtime or state changes, is provided.

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 very short (one sentence), but it is ambiguous and fails to clearly convey the action. Conciseness is okay, but the lack of clarity reduces effectiveness.

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 tool with a single parameter and no output schema, the description should at least indicate what happens after a successful restart (e.g., return status, downtime). The current description is too minimal and does not provide enough context for an agent to use the tool correctly.

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 100% description coverage for the single parameter 'id', which is described as 'App unique identifier (Base62-encoded UUID)'. The tool description adds no additional meaning, so the 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 tool name 'kill_master' suggests termination, but the description says 'Restart the Application Master'. This mismatch creates confusion about the actual action, making the purpose unclear. A specific verb and resource is stated, but the inconsistency undermines clarity.

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?

There is no guidance on when to use this tool versus alternatives like ncloud_dataforest_kill_container or other Data Forest management tools. The description does not specify prerequisites or context for restarting the Application Master.

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