update_task

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

With no annotations provided, the description carries full burden for behavioral disclosure. It merely states 'Update a task' without explaining whether updates are partial or full, what side effects occur, or any permission requirements. This is insufficient for a mutation tool with multiple optional parameters.

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 concise at one sentence, but it is under-specified given the tool's complexity (6 parameters, no annotations, no output schema). It could benefit from additional structure to improve clarity.

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 has 6 parameters, one enum, no output schema, and no annotations, the description is incomplete. It fails to explain return values, error handling, or the update behavior (e.g., merging vs replacing). The tool's specification is not adequately closed by the description alone.

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%, so baseline is 3. The description adds no additional meaning beyond the parameter descriptions provided in the schema. It does not clarify parameter interactions or provide usage examples.

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 'Update a task' uses a specific verb and resource, clearly indicating the tool's purpose. It is differentiated from siblings like create_task, delete_task, and move_task by the name itself. However, it is somewhat tautological as it restates the name without additional context.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, contexts, or situations where update should not be used. The description offers no comparative guidance against sibling tools like delete_task or move_task.

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