tasks_tasklists_update

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

Annotations only provide readOnlyHint=false, indicating mutation. The description adds the important behavioral detail that only supplied fields change (PATCH-like behavior), which is not evident from annotations alone. However, it does not disclose potential side effects or error conditions.

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, compact sentence that communicates the essential purpose and key behavioral trait. No redundant or irrelevant information.

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?

Given the tool's simplicity (2 parameters, no output schema), the description is sufficient: it states the action and partial update behavior. It could mention that the tasklist ID is required, but that is already in the schema. A minor gap: what the tool returns is unspecified, but no output schema exists.

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 100% with both parameters described. The description adds the partial update context, which marginally clarifies parameter usage (title is optional). With complete schema, baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 clearly states the tool updates a task list and specifies partial update behavior ('only supplied fields change'). This distinguishes it from sibling tools like tasks_tasklists_insert (create) and tasks_tasklists_delete (delete), making the purpose 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 description implies usage for updating an existing task list, but does not explicitly state when to use this tool versus alternatives like tasks_tasklists_insert or tasks_tasklists_delete. No guidance on when not to use or prerequisites.

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