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

With no annotations the description carries the full burden, and it discloses two non-obvious traits: item ordering, and that checklists already instantiated from the template keep their own copy (snapshot semantics). It omits whether replace discards the template's prior items wholesale and says nothing about permissions or auth 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?

Three tight sentences: the action and its two modes first, then item semantics, then the non-obvious snapshot behavior. No filler, and every sentence contributes information the agent needs.

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?

An output schema exists, so return values need no explanation, and the description covers the mutation's key semantics for a 6-parameter tool. For a no-annotation mutation, it could still say what a replace does to existing template content and whether elevated permissions are needed.

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 coverage is only 17%, so the description has to compensate. It does add meaning for checklist_template_id (activates replace mode), for items ordering, and for the required-item default and its consequence of blocking job/visit completion. But shop_id, name, and description get no treatment beyond their schema types.

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?

States a specific verb and resource ('Create a checklist template, or replace one') and gives the exact condition that selects replace mode ('give checklist_template_id'). The word 'template' plus the explicit upsert mode separates it from checklists_create, checklists_listTemplates, and checklists_archiveTemplate.

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 create-vs-replace branch is explicitly routed by the presence of checklist_template_id, which is the main decision an agent faces here. It does not name alternative tools or state exclusions (e.g., when to use checklists_archiveTemplate instead), so it stops short of a 5.

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