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

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

The description adds behavioral context beyond the annotations by explaining the consequence: 'the bot will not send what it was going to.' The annotations already mark the operation as destructive, so the description contributes additional semantic detail about the effect, though it does not cover edge cases or permissions.

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 a single, front-loaded sentence that immediately states the verb 'Снимает' (removes). It is compact with no filler, every word contributes to the meaning.

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 tool's simplicity, the description combined with the schema and annotations provides sufficient information for an agent to invoke it. It lacks information about error cases (e.g., task not found) but that is not critical for a basic cancellation tool. The description fully explains the core action and its effect.

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 description itself makes no mention of the parameters, but the input schema provides complete descriptions for both 'case' (default/fallback behavior) and 'task_id' (identifier from tasks_list). Since schema_coverage is 100%, the description is not required to compensate, so a baseline 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 that the tool 'removes a scheduled action: the bot will not send what it was going to' (Снимает запланированное действие). The title 'Cancel delayed action' aligns perfectly. This is distinct from tasks_list and other sibling tools, making the 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 provides no explicit guidance on when to use this tool versus alternatives, or conditions under which it should not be used. The usage is implied from the purpose, but no explicit context or exclusions are given. Therefore it falls at the 'implied usage' level.

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