hcm_update_absence

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

The readOnlyHint annotation (false) and the word 'Update' are consistent, but the description adds little beyond that. It does not disclose what the update does, what 'approval unless --write' means, whether it requires special permissions, or what side effects occur.

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 very brief with no wasted words, but the cryptic parenthetical undermines clarity. It is short but not well-structured to convey the tool's key behavioral distinction.

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 an opaque body object, no output schema, minimal annotations, and many related siblings, this description is far too thin. Agents cannot determine required body contents, the meaning of '--write', or how this differs from approval-specific tools.

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 0% and the description adds no meaning to the two parameters. The 'body' is an unconstrained object with no explained fields, and 'absenceId' is not described beyond its name, leaving agents to guess what to provide.

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 phrase 'Update an absence' identifies a specific verb and resource, and it is clearly distinct from create/delete absence siblings. However, the parenthetical '(approval unless --write)' is cryptic and may confuse agents about whether this is an update or an approval action.

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 on when to use this tool versus alternatives like hcm_approve_write, hcm_deny_write, or hcm_update_task_status. The parenthetical hints at a mode distinction but does not explain selection criteria or exclusions.

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