ncloud_functions_unlink_trigger_action

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

The description includes a warning emoji and explicitly labels the operation as 'Destructive', which adds behavioral context beyond the annotation's destructiveHint=true. It also explains the confirm parameter's role in executing the destructive 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: two short phrases that convey purpose, destructiveness, and usage requirement. Every word adds value with no unnecessary content.

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?

The description lacks explanation about the return value (no output schema) and does not mention prerequisites like the existence of the trigger and action. For a destructive tool, additional context about potential effects on the trigger state would be helpful.

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 all 4 parameters. The description adds no additional details about the parameters beyond what is already in the schema, so it meets the baseline but does not exceed it.

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 action ('Unlink'), the resource ('action from a trigger'), and includes a warning about destructiveness. It directly distinguishes from sibling tools like ncloud_functions_link_trigger_action by using 'Unlink'.

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 explicitly instructs to set confirm=true to execute, providing clear usage guidance. It does not explicitly state when not to use or mention alternatives, but the context of unlinking is sufficiently clear.

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