ncloud_datafence_cancel_file_export

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the destructive warning is largely redundant. The description adds the confirm=true execution gate, but that is also documented in the schema parameter description, and it does not explain consequences, reversibility, or idempotency behavior.

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?

Two short sentences with the warning front-loaded and no filler. Every clause is operational and the structure makes the destructive nature immediately visible.

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 a destructive state-changing tool with annotated safety hints and full schema coverage, the description covers purpose and confirmation. However, it omits the distinction from reject_file_export and any prerequisite about export approval state, which an agent needs to select the right sibling.

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 all four parameters including confirm are already documented. The description only echoes confirm=true and adds no syntax, format, or relationship details 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?

States a specific verb 'Cancel' and resource 'pending file export request,' so the action itself is unambiguous. It does not differentiate from the sibling ncloud_datafence_reject_file_export, which also terminates a pending export, leaving a selection ambiguity.

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?

Provides no when-to-use guidance, no prerequisites, and no alternatives; 'Set confirm=true to execute' is invocation mechanics rather than usage context. An agent must infer that this tool applies only to pending export requests and choose between it and reject_file_export on its own.

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