ncloud_mailer_delete_template

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

Annotations already declare destructiveHint and idempotentHint, and the description adds genuinely new context: it is a soft delete (isUse=false), reversible via ncloud_mailer_restore_template, and requires confirm=true to execute. This reveals behavior an agent could not infer from annotations or schema alone.

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?

Front-loaded with the most decision-relevant information (legacy status and alternatives), then the action, then the destructive caveat. Each clause earns its place—deprecation, availability window, soft-delete semantics, reversibility, and confirmation guard—with no filler.

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?

Complete for a destructive legacy delete tool: covers what it does, deprecation date, migration constraints, modern alternatives, reversibility, and the confirmation gate. Nothing needed for correct invocation is missing, and no output schema is necessary for a delete operation.

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 clear per-parameter descriptions, so the baseline 3 applies. The description reinforces 'Set confirm=true to execute', but this adds no substantive meaning beyond the confirm parameter's existing schema description.

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?

Description states a specific verb and resource: 'Delete a mail template (DELETE /template/{templateSid})'. It clearly differentiates from sibling tools like ncloud_mailer_restore_template, ncloud_mailer_create_template, and other delete operations (category, address book) by naming the target resource precisely.

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?

Explicitly marks the tool as legacy, states availability restrictions (migrated projects only, ~12 months until Dec 2027), and redirects new work to ncloud_sens_send_mail / ncloud_sens_list_mail_requests. Also names the undo path via ncloud_mailer_restore_template, giving an agent full decision context.

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