ncloud_hadoop_delete_notebook

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

Annotations already declare destructiveHint and idempotentHint. The description adds 'permanently' and the confirm gate, which are useful behavioral details. However, it does not disclose potential side effects, permission requirements, or recovery options, so it provides only modest added value beyond 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 immediately warns of destructiveness, states the action and resource, and specifies the confirmation requirement. No unnecessary words.

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 operation, the description paired with annotations and schema is largely complete. It conveys the permanent nature, the mandatory confirm flag, and the target instance number is in the schema. It could mention irreversibility or post-deletion effects more explicitly, but 'permanently' covers the core concern.

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%, so the schema already fully documents all three parameters. The description reinforces the confirm parameter's role as a required safety switch, but adds no new semantic information about regionCode or cloudHadoopNotebookInstanceNo 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 ('Permanently delete') and the resource ('Cloud Hadoop notebook'), distinguishing it from sibling tools like ncloud_hadoop_delete_cluster. The warning prefix and confirm requirement add specificity.

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 implicitly conveys when to use this tool (to delete a specific notebook) and explicitly requires confirm=true to proceed. It does not explicitly name alternatives for other operations, but the delete intent is unmistakable.

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