⚠️ TrxPromo: start promotion

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

Annotations indicate destructiveHint=true, but description adds context: 'Affects price/spend: the promotion fee is added on top of the base commission.' It also details error codes (1001/1002) and response includes success flag per listing. The dryRun and idempotencyKey behaviors are well explained.

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 moderately concise with useful information, front-loaded with purpose. Slightly lengthy due to param details but no wasted sentences.

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?

Despite no output schema, it describes response (success flag, error codes, allowed range). Parameters fully documented, sibling tools referenced. Covers prerequisites, error handling, and safety features.

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%, but description adds significant meaning: explains items format with required fields (itemID, commission, dateFrom, dateTo) and references external swagger. dryRun and idempotencyKey have version notes and default behaviors.

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 'Applies transactional promo/promotion with a pay-per-result commission to listings', clearly identifying the verb (apply) and resource (promotion on listings). It distinguishes from siblings like trxpromo_cancel and trxpromo_get_commissions by referencing them explicitly.

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 check limits via trxpromo_get_commissions before using, and to cancel with trxpromo_cancel. It also mentions error code conditions (validation vs promo unavailable) and response structure, guiding appropriate usage.

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