Delete chat templates

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

The annotations already declare destructiveHint=true, and the description merely repeats 'Destructive' without adding any new behavioral context. It fails to mention irreversibility, permissions, or side effects on related data. Since annotations already cover safety, the description contributes no additional 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 extremely concise: two short sentences. The first states the core function clearly, and the second adds a cautionary warning. There is no unnecessary prose or repetition of schema details, making it very efficient.

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?

This is a simple delete tool with one parameter and destructive annotations. The description covers the key aspects: what it deletes and that it is destructive. It does not explain where template IDs come from or error behavior, but for a low-complexity tool with sufficient annotations, this is mostly adequate. The lack of output schema and simple input reduce the need for additional detail.

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 0%, so the description should compensate by explaining the parameter structure. It only says 'Delete one or more templates,' which is a high-level restatement of the schema. The array structure with an 'id' field is self-evident from the schema, but the description adds no specific guidance about how to identify templates or handle invalid IDs.

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 action 'Delete' and the resource 'templates', specifying that one or more can be deleted. This distinguishes it from sibling tools such as kommo_templates_delete_one, which deletes a single template. The purpose is unambiguous and immediately understandable.

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. It does not mention kommo_templates_delete_one or any other sibling tools, nor does it state prerequisites or exclusions. The phrase 'one or more' implies batch usage, but this is implicit at best.

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