Update chat templates

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

Annotations provide openWorldHint and idempotentHint, but the description adds little beyond 'batch' and does not disclose overwrite semantics, required identifiers, partial-failure behavior, or whether updates are full replacements. For a mutating tool, this is thin.

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 with no filler; every word contributes meaning. However, it is extremely sparse given the complexity of a batch update operation.

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?

With a vague input schema, no output schema, and no behavioral detail, the description is insufficient for confident invocation. Critical aspects like payload item structure and update semantics are entirely unaddressed.

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 has 0% description coverage and the lone 'templates' parameter is a generic array of arbitrary objects. The description does not explain what each object should contain (e.g., template id, fields to update), so the agent cannot construct a valid request.

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 the action ('Edit'), resource ('chat templates'), and scope ('in batch'), making it clear this is a bulk update tool. It distinguishes itself from sibling create/delete/get/list operations, though it doesn't detail which template fields can be changed.

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 alternatives, no prerequisites are mentioned, and there is no mention of single-template updates or relationship to related tools. The only implied use case is editing multiple templates at once.

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