ncloud_dataflow_delete_workflow

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

Annotations already indicate destructiveHint and idempotentHint. The description adds the confirm safety mechanism, explicitly stating that the action is destructive and requires confirmation. It does not contradict annotations and provides useful behavioral context beyond what annotations offer.

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, using two short sentences. It front-loads a warning emoji and 'Destructive:' to immediately convey the critical nature. Every word 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?

For a simple delete tool with no output schema and full parameter coverage, the description covers the basics. However, it omits potential prerequisites (e.g., workflow must exist, must not be running) and does not mention the asynchronous nature or error conditions. Additional context would improve completeness.

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% with parameter descriptions already present. The description essentially repeats the confirm parameter's schema description ('Set confirm=true to execute'). No additional semantic meaning is added beyond the 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 action: 'Delete a Data Flow workflow permanently.' It specifies the resource (Data Flow workflow) and the permanence of the operation. Among sibling tools, it uniquely identifies the delete operation for workflows.

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 usage hint for the confirm parameter ('Set confirm=true to execute') but does not offer guidance on when to use this tool versus alternatives (e.g., other delete tools or non-destructive actions). No explicit when-to-use or when-not-to-use context is given.

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