ncloud_mailer_delete_unsubscribers

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

Annotations already mark destructiveHint and idempotentHint, but the description adds meaningful behavior beyond that: the operation re-enables advertising mail, maps to DELETE /unsubscribers with a JSON body, and requires confirm=true before execution. This strongly signals the destructive effect and the safety guard.

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 dense but not bloated: migration context, deadline, alternative tools, and the safety caveat all earn their place. The action is not front-loaded, but the warning is prominent and the length is justified by the legacy/transition context.

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?

With a simple 3-parameter schema, no output schema, and annotations covering safety, the description supplies the remaining needed context: availability window, exact effect, HTTP route, and the confirm guard. It could mention sibling unsubscribe-management operations, but it is otherwise complete for selecting and invoking the tool.

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 description coverage is 100%, so the schema fully documents all three parameters. The description only restates the confirm=true requirement, which adds no meaning beyond the parameter 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 states a specific action and resource: 'Remove addresses from the unsubscribe list' via 'DELETE /unsubscribers', and explains the consequence (addresses can receive advertising mail again). This clearly distinguishes it from the inverse sibling ncloud_mailer_register_unsubscribers even though that sibling is not named.

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 provides clear eligibility and timing context: available only to projects migrated from Cloud Outbound Mailer and only for about 12 months. It also points to SENS mail send/lookup alternatives, but it does not explicitly state when not to use this tool or name direct alternatives for unsubscribe management.

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