ncloud_dataflow_create_trigger

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

The annotations already indicate destructiveHint: false. The description ('Create') adds no behavioral details beyond what is implied by the verb. It does not disclose any side effects, prerequisites, or idempotency. 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 a single, front-loaded sentence that clearly conveys the tool's purpose. Every word serves a purpose, with no filler or redundant information.

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 is minimal but covers the basic purpose. It does not explain the difference between trigger types (CRON vs EVENT) or the behavior of parameters like dryRun or enabled. Given the absence of an output schema and 7 parameters, more context would be beneficial, but the schema descriptions partially compensate.

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% for all 7 parameters. The description adds no additional meaning beyond the schema field descriptions. Baseline 3 is appropriate since the schema already documents the parameters adequately.

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 ('Create'), the resource ('Data Flow trigger'), and the purpose ('scheduled or event-based job execution'). It effectively distinguishes this tool from sibling tools like ncloud_dataflow_list_triggers, ncloud_dataflow_get_trigger, and ncloud_dataflow_delete_trigger.

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 implies usage for creating scheduled or event-based triggers, but it does not explicitly state when to use this tool versus alternatives (e.g., ncloud_functions_create_trigger) or when not to use it. No exclusions or alternative tools are mentioned.

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