ncloud_mailer_delete_category

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 important behavioral constraints: only empty categories can be deleted, and confirm=true is required to execute. It also repeats the destructive warning. This goes beyond the annotations without contradicting them.

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 relatively long but each part earns its place: legacy context, destructive warning, the operation, and the confirm flag. It is front-loaded with the migration note, which is important for routing, and remains readable.

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?

It covers the endpoint, the precondition (empty category), the confirm flag, the legacy status, and the new API alternatives. For a delete operation without an output schema, nothing critical is missing for an agent to call it correctly.

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 all parameters have descriptions. The description adds the empty-category constraint on categorySid and reinforces the confirm=true requirement, which is not fully captured in the schema. This enriches parameter understanding.

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 states a specific verb and resource: 'Delete a template category (DELETE /category/{categorySid})'. It also adds critical context—legacy API, migration status, and the requirement that the category must be empty—making the purpose unmistakable and distinct from sibling delete operations.

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?

It clearly states when this tool applies: only to projects migrated from Cloud Outbound Mailer, and for a limited time. It also references the newer SENS alternatives for sending/lookup. However, it does not explicitly name an alternative for category deletion specifically, leaving some inference to the agent.

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