ncloud_delete_bucket_encryption

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

Annotations already mark the tool as destructive and idempotent. The description adds value by explaining the specific consequence—new objects will no longer be encrypted by default—beyond the annotation flags. No contradiction exists; the description aligns with and enriches the 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?

Two sentences with a clear caution emoji, immediately stating the action and effect. Front-loaded with key information, no redundancy. Every sentence contributes meaning.

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, two-parameter destructive tool with idempotent hint and no output schema, the description fully covers the purpose, effect, and execution requirement. No further context is necessary.

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 both parameters fully described. The description reiterates the confirm parameter's role but does not add new semantic detail. Baseline score of 3 is appropriate as the description adds minimal value 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 specifies exactly what the tool does: delete the default server-side encryption configuration from a Ncloud Storage bucket, with a clear effect on future objects. The verb 'delete' and resource 'bucket encryption' are distinct, especially among sibling tools like ncloud_get_bucket_encryption and ncloud_put_bucket_encryption.

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 includes a caution about destructiveness and the requirement to set confirm=true, but does not explicitly guide when to choose this tool over alternatives like ncloud_put_bucket_encryption or ncloud_get_bucket_encryption. Usage context is implied rather than explicit.

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