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

No annotations, so the description carries the full load. It usefully discloses two behavioral facts: templates are returned with their items nested, and archived templates are hidden unless opted in. It says nothing about read-only safety, result size, or ordering/pagination for what could be a large template set.

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?

Two short sentences, no filler, with the archived-filter rule placed where it will be read. The telegraphic phrasing is efficient but slightly clipped, and the primary action is never stated as a verb.

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 format needn't be spelled out, and the tool is simple (2 params). Still, the description omits what 'items' means in practice and gives no hint about ordering or volume, which are the main unknowns for a template-listing call.

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 0%, so the description must compensate. It does explain include_archived meaningfully (default excludes archived, opt-in includes them), but shop_id — the required scope parameter — is never described beyond its obvious name, leaving half the surface documented only by inference.

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?

Names the specific resource ('checklist templates') and states that items are included, which separates it from checklists_get and checklists_list (instances). It's a noun phrase rather than a verb, so the 'list' operation is inferred from the name, but the resource and scope are unambiguous.

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 clause 'Archived ones only with include_archived' gives a concrete selection rule for one parameter, but there is no explicit when-to-use vs. siblings such as checklists_get or forms_listTemplates, and no stated prerequisites. Usage is implied rather than guided.

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