hcm_update_task_status

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

Annotations only provide readOnlyHint=false, which aligns with 'Update', but the description adds no behavioral context: no mention of required permissions, irreversibility, side effects on dependent data, or response behavior. With no other annotations, the description carries the full disclosure burden and does not meet it.

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 one compact sentence with no filler. The key action is front-loaded and the endpoint path is additive, though the format is so terse that it reads more like a stub than a polished tool description.

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 four parameters including a nested 'body' object, no output schema, and effective mutation semantics, the description is materially incomplete. An agent cannot determine the body shape, valid status transitions, or what handling is required after invoking this 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 description coverage is only 25%, with status being the only parameter explained. The description does not compensate: it says nothing about what 'body' should contain, how taskId and checklistId relate to the endpoint path, or what status values beyond the schema example are accepted.

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 names a specific verb and resource: 'Update checklist task status', and adds the endpoint path 'child/allocatedTasks/.../action/updateTaskStatus'. This distinguishes it from other hcm_update_* siblings, though the path fragment is cryptic and the wording partly restates the tool name.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention related checklist tools like hcm_allocate_checklist or hcm_force_close_checklist, nor does it state any preconditions or scenarios where this status update applies.

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