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

With no annotations, the description carries the burden well by disclosing the gating semantics: a visit checklist blocks that visit's done, a job checklist blocks jobs.complete, and the job also waits on checklists of not-yet-done visits. That is non-obvious production behavior an agent could not infer from the schema. Missing: whether a duplicate checklist on the same job/visit errors, and any permission 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 short sentences, each carrying distinct information, with the core action front-loaded and consequences following. No filler or repetition of schema facts.

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 completes the picture with the done-gating behavior. The remaining gap is edge-case behavior on duplicate or conflicting checklists, which is minor for a create tool at this complexity.

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 only 17% (only items.required and signoff_required are documented), so the description must compensate. It explains visit_id and checklist_template_id as a mutually exclusive choice and clarifies items as the alternative source, covering the parameters that matter most; it adds little for name, which is self-evident.

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?

Opens with a specific verb+resource ('Put a checklist on a job, or on one visit') and immediately distinguishes the two attachment scopes. It does not name sibling tools (checklists_saveTemplate, checklists_addItems) explicitly, but the creation/attachment framing is distinct enough that an agent can tell it from template or item-management tools.

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?

Gives clear selection logic for the tool's own modes: attach to job vs. one visit via visit_id, and populate via template (checklist_template_id) or inline items. It also states the downstream consequence of each choice (visit gate vs. jobs.complete gate), which guides the decision. No explicit alternatives or exclusions against sibling tools.

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