ncloud_dataflow_delete_trigger

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds context by stating 'permanently' and requiring confirm=true, which goes beyond the annotation flags. It does not elaborate on consequences like irreversibility or error on non-existent trigger, but given the annotation coverage, it is adequate.

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 note, front-loaded with a warning icon and 'Destructive'. Every word earns its place with no redundancy. Highly efficient.

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?

Given the simple operation (delete), the description covers the essential aspects: what it does, that it requires confirmation, and that it's destructive. With no output schema, the description need not explain return values. The idempotency hint is provided via annotations. Overall, it is complete for the tool's complexity.

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%, so the baseline is 3. The description does not add additional meaning beyond the schema for the parameters; it repeats the confirm requirement already in the schema. Thus, no extra semantic value is provided.

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 tool deletes a Data Flow trigger permanently, using the verb 'Delete' and specifying 'permanently'. It includes a warning icon and 'Destructive' to emphasize the action, distinguishing it from sibling tools like create, get, and list triggers.

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 explicitly instructs to set confirm=true to execute the deletion, providing a clear prerequisite. It warns that the operation is destructive, but does not explicitly state when to use this tool versus alternatives (e.g., disabling a trigger). However, the context is sufficiently clear for a delete operation.

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