Delete chat template

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

The description repeats 'Destructive,' which is already captured by the destructiveHint annotation. It adds no additional behavioral context such as irreversibility, cascade effects, or authorization requirements.

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 with two short sentences. Every word serves a purpose and the key information is front-loaded.

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 delete operation, the description covers the core action but lacks details about return values, error behavior, and differentiation from the sibling delete tool. This makes it adequate but not fully complete in context.

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 schema has 0% description coverage, so the description's 'by ID' clarifies that the 'id' parameter is the template identifier. However, it does not provide further details like source, format, or typical usage, making it minimally compensating.

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 'Delete a single template by ID' with a specific verb and resource. It is unambiguous about the operation, though it does not explicitly distinguish from the sibling tool 'kommo_templates_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?

No guidance is provided on when to use this tool versus the similarly named 'kommo_templates_delete' or other delete tools. The sibling list reveals potential ambiguity without further context.

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