weeek_update_task

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

The description discloses it is a WRITE OPERATION and warns the MCP client may prompt for confirmation. It notes that only provided fields are sent and omitted fields remain unchanged. Without annotations, this adds good behavioral context, though it could mention error handling or idempotency.

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?

Description is concise with 5 sentences, front-loaded with the main action, and each sentence provides essential information without fluff. Warnings are placed logically.

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?

No output schema, but description states 'Returns the updated task', which is sufficient. Covers required and optional parameters, and separates concerns by referencing sibling tools. Complete for a simple update tool.

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 baseline is 3. The description adds value by summarizing which parameters are optional and the partial-update behavior. However, there is a minor mismatch: description refers to 'due_date' while schema uses 'date_end', which could cause confusion.

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 editable fields of an EXISTING task in WEEEK' with specific editable fields listed. It distinguishes from sibling tools by explicitly mentioning not to move or complete tasks, referencing weeek_move_task and weeek_complete_task.

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 explicit when-not-to-use guidance: 'Do NOT use this to move tasks between columns (use weeek_move_task) or to mark tasks complete (use weeek_complete_task).' Also specifies that task_id must come from weeek_list_tasks, giving a clear prerequisite.

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