update_task

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

There are no annotations, so the description must carry the behavioral burden. It does add useful constraints: avoid column-moving behavior and keep title/description in English. However, it does not disclose mutation effects, validation behavior, idempotency, error behavior, or what happens when multiple/differing identifiers are supplied.

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 compact and front-loaded with the core action. Each sentence earns its place: the main purpose, the exclusion, the identifier rule, and the language constraint. There is no redundant wording.

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?

For a tool with 10 optional parameters, no required fields, no annotations, and no output schema, the description provides enough to call it in basic cases but leaves important gaps. It does not clarify whether updates are partial or full replacement, what happens if both taskId and taskNumber are provided, or what the response/error behavior looks like.

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 already covers all parameters (100% coverage), so the baseline is 3. The description adds value beyond the schema by requiring title/description to be in English and clarifying the acceptable identifier pair 'taskId OR taskNumber', which is important for correct invocation.

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 states a specific verb and resource: 'Update task properties.' It also distinguishes itself by explicitly saying not to use it for moving columns, making it easy for an agent to separate from start_task/complete_ai_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?

It gives an explicit when-not-to-use instruction ('Do NOT use this to move columns') and names the intended alternatives ('use start_task/complete_ai_task instead'). It also notes that taskId OR taskNumber can be used, which is practical selection guidance.

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