ncloud_delete_monitor_group_force

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

Annotations already signal destructiveness; description adds context about the scope ('ALL event rules') and irreversibility, which is valuable behavioral information beyond the 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?

Single sentence with warning emoji, front-loaded, no wasted words. Every sentence earns its place.

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?

Adequately describes what gets deleted and the destructive nature. Could mention return value or post-deletion state, but not necessary given no output schema. Sufficient for a destructive operation.

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%, baseline 3. Description adds useful context for 'confirm' parameter (must be true to execute) and clarifies 'monitorGroupId' purpose, providing extra meaning beyond schema.

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 ('Force delete'), the resource ('event rules associated with a specific monitoring target group'), emphasizes destructiveness and irreversibility, and distinguishes from sibling tools like ncloud_delete_monitor_group.

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?

Implied usage: for force deleting event rules, not the group itself. But lacks explicit when-to-use vs alternatives or when-not-to-use guidance.

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