ncloud_put_scheduled_action

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

With empty annotations, the description carries the full burden of behavioral disclosure. It merely says 'Create or update' without explaining important semantics: whether an existing scheduled action is fully replaced, whether all parameters are required for updates, or how one-time vs recurring schedules interact. For a mutation tool, this is a significant transparency gap.

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 a single sentence of ten words, front-loaded with the action verb. Every word earns its place, and there is no redundancy or fluff.

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 tool has 8 parameters, no output schema, and no annotations, yet the description provides minimal context. It does not explain scheduling concepts (one-time vs recurring using recurrenceInKST), the effect of updating an existing action, or expected response/behavior. For a complex ASG scheduling operation, this is incomplete.

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 provides 100% coverage with meaningful descriptions for all 8 parameters, so the baseline is 3. The description adds no additional parameter-level detail beyond what the schema already states, so no extra credit is warranted.

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 states a specific verb ('Create or update') and resource ('a scheduled action for an Auto Scaling Group'). This clearly distinguishes it from sibling tools like ncloud_list_scheduled_actions and ncloud_delete_scheduled_action, and also from ncloud_put_scaling_policy which targets a different resource type.

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 phrase 'Create or update' and the resource type, but the description does not explicitly state when to use this tool versus alternatives or mention any exclusions or preconditions. There is no guidance on choosing between this and related tools like delete_scheduled_action or put_scaling_policy, though the resource clarity partially compensates.

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