ncloud_ncs_delete_object

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

Annotations already mark as destructive and idempotent. The description adds value by warning with an emoji, specifying 'Permanently delete,' and explaining the confirm parameter as a guard. It does not detail edge cases (e.g., behavior if object not found) but adequately covers the essential behavioral trait.

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 line with a warning emoji, clear action, resource, and instruction. Every word is essential, no redundancy.

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 destructive operation, the description covers the core action, safety guard, and participant context. It lacks detail on return values or error cases, but that is acceptable given the simplicity and presence of annotations for safety and idempotency.

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?

The input schema has 100% description coverage for all three parameters (bucketName, key, confirm). The tool description only repeats 'Set confirm=true to execute,' adding no new meaning beyond the schema descriptions. Thus, baseline score of 3 applies.

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 a Ncloud Storage bucket,' specifying the verb (delete), resource (object in NCS bucket), and the destructive nature. It distinguishes from siblings like ncloud_delete_object by specifically mentioning Ncloud Storage (NCS) and the confirm safeguard.

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 clear instruction: 'Set confirm=true to execute,' which is a critical usage guideline for safety. However, it lacks explicit guidance on when to use this tool versus alternative delete tools (e.g., ncloud_delete_object), though the NCS prefix provides implicit differentiation.

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