⚠️ TrxPromo: остановить

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

The description states that the tool stops promotion, which is a mutation operation. Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds little beyond the annotations; it does not explain side effects or the impact of stopping a promotion. However, the dryRun and idempotencyKey parameters (documented in schema) provide some transparency.

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 very concise—one sentence that states the core function. It is appropriately front-loaded. While it could be expanded slightly with usage context, it is not overly verbose.

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 complexity (no output schema, annotations present), the description is minimal. It explains the action but does not describe the output or any conditions for success. The presence of dryRun and idempotencyKey hints at safety features, but the description fails to connect them. Sibling tools exist, but no comparative guidance is given.

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?

The input schema has 100% parameter description coverage, so the description does not need to add much. It adds no parameter information beyond what the schema already provides. The baseline of 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 clearly states the tool's action: it stops transactional promotion for ads. The verb 'останавливает' is specific and distinguishes it from siblings like trxpromo_apply, which presumably starts promotion. The resource is clearly 'транзакционное продвижение для объявлений'.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. The only clue is the action itself, but no explicit context is given.

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