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

No annotations are provided, so the description carries the full burden. It discloses append-at-end behavior and alludes to locking via "same locks as ticking," but that reference is opaque—it never says what the locks are, what permission or concurrency constraints apply, whether duplicates are allowed, or what happens on failure.

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 tight sentences with the core action and scope front-loaded. Nothing is wasted, though "same locks as ticking" is a cryptic aside that spends words without clarifying.

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 not be described. However, for a mutation tool with no annotations, the description omits permission model, lock semantics, item limits, and failure behavior—gaps an agent needs to call it safely.

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 0% and the description says nothing about either parameter. It does not explain the items array shape (label/required), the 1–200 item limits, or what checklist_id must reference, leaving the agent to infer everything from the raw schema.

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 (add items) plus an ordering detail (to the end) and scope (owner or office checklists). It distinguishes itself from sibling checklists tools like checkItem and create, though it does not explicitly name which sibling to use instead.

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?

"(owner or office)" hints at which checklist kinds this applies to, and "Same locks as ticking" points at checklists_checkItem as a related operation. There is no explicit when-to-use/when-not or prerequisites, so the guidance is only implied.

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