todoist_task_update

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

With no annotations provided, the description must disclose behavioral traits. It mentions the update action and a parameter dependency (duration requires due_string with time), but it does not explain partial update behavior, reversibility, conflict handling, or error scenarios. This is insufficient for a 15-parameter tool.

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 two sentences: one states the purpose and identification method, the other lists supported fields. Every sentence contributes essential information without redundancy, making it both concise and front-loaded.

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 15 parameters, no output schema, and no annotations, the description is too sparse. It omits details about return values, behavior on missing or multiple matches, error handling, and the fact that all fields are optional (though implied by schema). More context is needed for effective use.

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 100%, so the baseline is 3. The description adds value by summarizing the categories of fields, but the schema already provides detailed descriptions for each parameter. The description does not add substantial meaning beyond the 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?

The description clearly states the tool updates an existing task, identifies tasks by ID or partial name search, and lists the supported fields. This specificity effectively distinguishes it from sibling tools like todoist_task_create or todoist_task_delete.

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 provides context on when to use (updating an existing task) and how to identify the task (by ID or partial name), but it does not explicitly state when not to use it or mention alternatives like specialized update tools (e.g., todoist_task_day_order_update).

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