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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent closed-world mutation. The description adds no behavioral context beyond the field list: it does not explain partial-update semantics, whether omitted fields stay unchanged, permission requirements, or what happens when status/assignee changes.

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 a single efficient sentence with the action and supported fields front-loaded. There is no redundant or filler 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?

The tool is a mutation with nine parameters, two required identifiers, and no output schema. The schema and annotations carry most of the context, but the description should at least mention identifier requirements and partial-update behavior; it also leaves out the priority field.

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 the parameter schema already provides meaning for all nine parameters. The description adds little beyond naming most editable fields, and it omits priority while not mentioning the required task_number and board_id identifiers.

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 gives a specific verb (edit) and resource (task), and it enumerates fields that can be changed. The purpose is clear, but it does not distinguish this tool from close siblings such as transition_task_status 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 phrase 'Use this to edit...' states purpose rather than usage guidance. It gives no conditions for choosing update_task over transition_task_status, move_task, or other task tools, and no prerequisites or exclusions are mentioned.

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