Create chat templates

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

With only openWorldHint annotation, the description carries the full burden of behavioral disclosure. 'Create' clearly implies a write operation, but there is no information about idempotency, validation, partial failure behavior, or what happens if templates already exist. No contradiction with annotations exists, but the description is too sparse.

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 short sentence, which is structurally clean, but it is under-specified. It seems more like a placeholder than a deliberate, concise explanation. Valuable information such as template structure and constraints is missing, so brevity is not an asset here.

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, one might argue a short description suffices, but this lacks critical context. There is no output schema, and the description does not mention return values, limits, or field requirements. For a creation operation, an agent needs more detail to correctly invoke the tool.

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 one parameter 'templates' with 0% description coverage. It is a generic array of objects with no property details. The description merely says 'chat templates' and does not compensate by explaining the structure or required fields for each template object. The agent is left without essential information to construct valid input.

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 tool's function: 'Create chat templates in batch.' It uses a specific verb ('Create') and resource ('chat templates') and distinguishes it from sibling tools like kommo_templates_update or kommo_templates_delete. The batch scope is an additional useful qualifier.

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 offers no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or situations where other tools (e.g., kommo_templates_update) would be more appropriate. The only implied context is 'batch', but that is not explicit enough.

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