⚠️ Discounts: send campaign

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

Discloses that the operation is irreversible, sends messages publicly, deducts money, and returns an error if funds insufficient. This adds significant context beyond the annotations (destructiveHint=true), including specific consequences and error conditions.

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?

Description is relatively short and front-loads warnings (⚠️, BETA, IRREVERSIBLE). Every sentence adds value, though slight redundancy could be trimmed. Efficient for a high-risk tool.

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?

Given the tool's destructive nature, missing output schema, and annotations providing minimal context, the description compensates fully. It explains workflow steps, consequences, error condition, and safe dryRun option, making the agent fully informed to use the tool safely.

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 baseline is 3. However, description adds context: dispatches are 'taken from the multi_create response', expiresAt is within range from multi_create, dryRun explains safety and default behavior, and idempotencyKey explains duplicate protection. This enriches parameter understanding 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 clearly states that this tool confirms and pays for a discount campaign created via msg_discounts_open_api_multi_create. It uses specific verbs ('confirms', 'PAYS') and resource ('discount campaign'), and distinguishes itself from read-only sibling tools like ..._available and ..._stats.

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 advises to confirm with user before calling, and contrasts with read-only methods that do not perform actual sends/charges. Also implies it should be used after multi_create, providing clear when-to-use and when-not-to-use guidance.

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