update_tasks

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

Given no annotations, the description discloses important behaviors such as recurrence creation on completed=true, tag replacement vs add/remove conflict, and date clearing with empty string. However, it omits mentioning that omitted fields remain unchanged (null default).

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 well-structured with a main sentence followed by a parameter list, though slightly verbose with 'Parameters (per item):' and some redundancy. Generally efficient.

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?

Covers all input fields and key behaviors, but lacks mention of batch limits or error handling. Output schema exists so return values are not needed. Good for complexity level.

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?

The schema has 0% description coverage, but the description compensates by explaining each parameter's semantics, including date format, tag conflict, and completed behavior on recurring tasks, adding significant value 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 'Update one or more tasks' with a verb and resource, and distinguishes from sibling tools like create_tasks and delete_tasks by specifying the update action.

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?

Provides clear context for use (updating tasks) and includes guidance on tag conflicts and status preference, but does not explicitly state when not to use this tool vs alternatives like create_tasks.

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