Update Task

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

With no annotations, the description carries the burden. It adds the key behavioral trait that only provided fields are changed, indicating a partial update. However, it doesn't disclose return value, permissions, or failure modes.

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 three short sentences, front-loaded with the core action, then requirements, then behavior. There is no wasted text.

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?

Despite having 14 parameters and no output schema or annotations, the description is minimal. It doesn't explain return values, use cases, or contrast with sibling update tools, leaving the agent with insufficient context for a complex 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?

The input schema provides full descriptions for all 14 parameters (100% coverage). The description adds value by clarifying that only the fields you provide will be changed, which helps agents understand that parameters are optional and updates are partial.

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 an existing task' with a specific verb and resource. It also specifies required parameters (task_id and project_id). However, it doesn't explicitly distinguish this tool from sibling update tools like complete_task or move_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?

The description provides prerequisites (both task_id and project_id are required) and the partial update behavior, which implies when to use it. But it doesn't provide explicit guidance on when to use this instead of alternatives like complete_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.