ncloud_dataflow_delete_job

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds a 'Destructive' warning and notes permanence, which reinforces but does not significantly extend beyond annotations. No contradiction. The confirm parameter behavior is already in the schema. Overall, limited added value.

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 with a warning emoji, two essential facts (action and confirm requirement), and zero filler. It is optimally concise and front-loaded, earning its place with no waste.

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 no output schema, the description does not explain return values. It covers the core action and confirm requirement but omits details like prerequisites (e.g., job existence, permissions) or idempotency behavior. For a destructive tool with annotations, it is minimally adequate but lacks 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 description coverage is 100%, and the description only reiterates that confirm must be true, which is already stated in the schema's property description. No new semantic information is provided about parameters beyond what the schema already conveys.

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') and the resource ('Data Flow job'), with the word 'permanently' emphasizing the effect. It is concise and directly conveys the tool's purpose, distinguishing it from other delete tools like ncloud_dataflow_delete_workflow by naming 'job' specifically.

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 specifies the mandatory confirm=true requirement, which is a key usage guideline. However, it does not provide when-to-use vs. alternatives (e.g., other delete tools) or when-not-to-use criteria. The guidance is minimal but functional.

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