⚠️ TrxPromo: stop

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

Annotations indicate destructiveHint=true, and the description confirms that the tool cancels and reverts effects, adding detail about response structure (success flag per listing) and error codes (1001 validation, 1002 promo unavailable). This goes beyond annotations without contradicting them.

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 brief, with only two sentences, yet covers purpose, revert effect, response info, error codes, and related tools. It is front-loaded with the primary action and efficiently conveys all necessary information.

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, the description adequately explains the response (success flag, error codes). It covers key aspects: idempotency key purpose, dry run behavior, and error handling. Combined with thorough annotations and schema, it provides complete context for tool use.

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 baseline is 3. The tool description does not add significant extra meaning to parameters beyond the schema, though the schema itself is well-described. No additional context is provided in the description for parameters.

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 the verb 'cancels' and the resource 'active and scheduled transactional promo for listings'. It distinguishes itself from sibling tools trxpromo_apply (applies promo) and trxpromo_get_commissions (read-only), making its purpose unambiguous.

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?

The description explicitly tells when to use alternatives: 'Apply promo again with trxpromo_apply; check commissions with trxpromo_get_commissions (read-only).' This provides clear guidance on when to use this tool vs. its siblings.

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