ncloud_livestation_stop_vod_channel

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the destructive nature is covered. The description adds genuinely new context beyond that: the concrete consequence ('playback is interrupted') and the confirm=true guard requirement, which is exactly the kind of behavioral detail annotations cannot express. It omits reversibility and auth requirements.

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?

A single sentence, front-loaded with the destructive warning and the concrete effect, followed by the execution guard. Every clause earns its place with zero waste.

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 two-parameter mutation tool with full annotation and schema coverage and no output schema, the description supplies the essential facts: what changes, the user-visible impact, and the safety gate. Only the reversibility/auth story is left implicit.

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 description coverage is 100%, so both parameters are already documented, and the description's mention of confirm=true merely echoes the schema. Baseline 3 is appropriate since the schema does the heavy lifting with no added syntax or format detail.

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 (turn off), resource (Live Station VOD-to-Live channel), and even the underlying API operation (vodchanneloff). This distinguishes it from the non-VOD ncloud_livestation_stop_channel sibling, though the description stops short of naming that sibling explicitly.

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?

Usage is implied by the word 'off' and the destructive warning, letting an agent infer this is a reversible stop rather than a delete. However, it never states when to prefer this over ncloud_livestation_delete_vod_channel or the plain stop_channel variant, leaving the choice to inference.

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