task_delete

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

Annotations already declare destructiveHint=true, so the destructive nature is known. The description adds value beyond annotations by explicitly requiring user confirmation, which is a meaningful behavioral constraint for an AI agent invoking a destructive operation. No contradiction with annotations.

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 extremely concise and front-loaded: the action 'Удалить задачу' appears first, followed by the only essential behavioral note. There is no filler or redundant 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?

For a simple one-parameter delete operation, the description plus annotations are nearly sufficient: it names the resource, requires user confirmation, and the schema covers parameters. A slightly richer mention of irreversibility or cascading effects would make it fully complete, but the confirmation requirement already covers the main risk.

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 fully documents the single required parameter 'id' with a clear description. The tool description adds no extra parameter-level detail, which is acceptable given 100% schema coverage.

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 states a specific verb ('Удалить' / delete) and a clear resource ('задачу' / task). This makes the tool's purpose unambiguous and naturally distinguishes it from siblings like task_get, task_update, task_complete, and crm_delete.

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 phrase 'Требует подтверждения пользователя' provides an important usage precondition: the agent should not invoke this tool without user confirmation. However, it does not explicitly compare this tool to alternatives or state when to prefer task_delete over task_update or task_complete.

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