ncloud_remove_port_plugin

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

The description includes a warning icon and 'Destructive', consistent with the destructiveHint annotation. It additionally emphasizes that confirm must be true to execute, which adds behavioral context beyond the annotations. No contradiction with annotations.

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—one sentence plus a brief instruction—with no wasted words. The warning is front-loaded, making critical information immediately visible.

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 covers the core action and the confirm requirement, which is sufficient given the annotations and schema coverage. However, it lacks context about the impact on the server instance or how this fits with related port plugin operations (e.g., after removal, monitoring is affected).

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 coverage is 100%, so parameters are already well-documented. The description only adds value for the confirm parameter by stating it must be true to execute. Other parameters (instanceNo, portList, type) are not elaborated further.

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 'Remove' and the resource 'port monitoring plugin(s) from a server instance', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like ncloud_add_port_plugin and ncloud_list_port_plugins by specifying removal.

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 advises setting confirm=true to execute, which is a key usage guideline. However, it does not provide guidance on when to use this tool versus alternatives (e.g., ncloud_set_port_plugins) or specify prerequisites or exclusions.

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