ncloud_delete_scheduled_action

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

Annotations include destructiveHint and idempotentHint. The description adds a safety mechanism (confirm flag) and a warning emoji, providing behavioral context beyond annotations. It does not contradict 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: a single sentence with a warning prefix and the critical instruction. Every word serves a purpose.

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 simple deletion tool with no output schema and full schema coverage, the description is adequate. It covers the action and the safety requirement, though it doesn't mention return values or typical outcomes.

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%, and the description adds no additional meaning to the parameters beyond what is already in the schema. 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 description clearly states it deletes a scheduled action from an Auto Scaling Group, using a specific verb and resource. It distinguishes itself from sibling tools like ncloud_put_scheduled_action and ncloud_list_scheduled_actions by its destructive nature.

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 provides a key guideline ('Set confirm=true to execute') but does not explicitly state when to use this tool versus alternatives or when not to use it. It assumes the agent knows the context.

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