Отменить отложенное действие

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the consequence ('бот не отправит то, что собирался'), which clarifies the effect of the mutation, but says nothing about required task state, permissions, or irreversibility. A 3 is appropriate given annotations carry most of the load.

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?

A single short sentence, front-loaded with the verb and resource, with zero filler. Slightly terse given it could have added a routing hint without bloat.

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?

For a two-parameter destructive tool with full schema coverage and annotations declaring destructiveness, the description is barely adequate. It covers the effect but omits task-state prerequisites, error behavior, and how it relates to the many cancel-flavored siblings, though the annotations and schema absorb much of that burden.

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 both parameters (case and task_id) are fully documented in the schema, including that task_id comes from tasks_list. The description adds no parameter-level detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('Снимает запланированное действие') and even names the effect ('бот не отправит то, что собирался'). An agent can tell this cancels a scheduled bot action, though it does not differentiate itself from similarly-named siblings like dialogs_cancel_scheduled or broadcasts_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?

The description gives no when-to-use context, no mention of tasks_list as the source of task_id, and no guidance on how it differs from dialogs_cancel_scheduled or broadcasts_cancel. Usage is only loosely implied by the phrase 'запланированное действие'.

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