⚠️ TrxPromo: start promotion

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

Discloses that promo fee is added on top of base commission, response includes success flag per listing, and error codes (1001 validation, 1002 promo unavailable) with allowed commission range. Adds value beyond annotations (destructiveHint=true, etc.) but could mention idempotency implications.

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?

Concise two-sentence description plus error details. Front-loaded with main action, no redundant info.

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?

Covers purpose, parameters, error handling, response shape, and related tools. No output schema but description adequately replaces it for the agent.

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?

All parameters described with clear syntax: commission in hundredths of a percent (1500=15%), date format YYYY-MM-DD, dryRun and idempotencyKey with detailed behavior. Schema coverage 100%, and description adds meaning beyond 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?

Clearly states 'Applies transactional promo/promotion with a pay-per-result commission to listings' with specific verb (applies), resource (promotion), and context (listings). Distinguishes from siblings by referencing trxpromo_get_commissions and trxpromo_cancel.

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 'First check the limits via trxpromo_get_commissions; cancel a running promo with trxpromo_cancel', providing clear prerequisites and when to use alternative tools.

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