ncloud_delete_object

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

Annotations already indicate destructiveHint=true, but the description adds the warning emoji, mentions 'Permanently', and clarifies the confirm parameter requirement. This provides additional behavioral context beyond annotations, such as the necessity of explicit confirmation for execution.

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: a single sentence with a warning emoji. It front-loads the destructive nature and immediately communicates the key requirement. No wasted 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 covers the essential behavioral points (destructive, permanent, confirm required). It lacks details on return values or error conditions, but no output schema exists and the tool is straightforward. Completeness is adequate.

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?

Input schema has 100% coverage with descriptions for all parameters. The description briefly repeats the confirm parameter usage ('Set confirm=true to execute'), but does not add new meaning beyond schema. Baseline 3 is appropriate.

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 'Permanently delete an object from an Object Storage bucket', specifying the verb (delete), resource (object), and scope (single object, bucket). It distinguishes from siblings like ncloud_delete_multiple_objects and ncloud_ncs_delete_object by specifying 'Object Storage' and focusing on a single object.

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 usage guidance by requiring 'confirm=true' to execute, but does not explicitly compare with alternatives or state when to use this tool over sibling tools. It relies on the tool name and context.

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