ncloud_hadoop_delete_notebook

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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds the detail that deletion is 'permanent' and requires confirmation, which goes beyond the annotations. No contradictions.

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 line with a warning emoji, the action, and the key condition. No superfluous words; front-loaded with critical information.

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 deletion tool with good annotations and schema coverage, the description adequately covers purpose, destructive nature, and confirm requirement. It does not explain return values, but that is acceptable for a delete operation with no output schema.

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 descriptions for all 3 parameters. The description reinforces the confirm parameter requirement but does not add significant new meaning 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'), the resource ('Cloud Hadoop notebook'), and the required condition ('Set confirm=true'). It is distinct from sibling tools like 'ncloud_hadoop_create_notebook' and 'ncloud_hadoop_list_notebooks'.

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 key usage condition ('Set confirm=true to execute') and a destructive warning, but lacks explicit guidance on when to use versus alternatives (e.g., soft delete or cluster deletion). It implies usage for permanent deletion but no exclusions.

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