hr_absence_cancel

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the row is never deleted, only its status changes, which is a key behavioral trait. It also mentions the required permission. However, it does not disclose side effects on related data, idempotency behavior, or error handling, but the core mutation semantics are clearly conveyed.

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 sentence with a parenthetical that adds essential context without padding. The core action is front-loaded, and the permission requirement is placed at the end, maintaining clarity and efficiency.

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 has three required parameters, no output schema, and no annotations. The description covers the core operation and permission but omits details like return value, idempotency semantics (despite the idempotencyKey parameter), and handling of already-cancelled absences. For a simple cancellation tool, this is acceptable but not fully complete.

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%, so the description must compensate by explaining the three parameters (workspaceId, absenceId, idempotencyKey). It does not mention any of them. The parameter names are self-explanatory to a human, but the description adds no meaning beyond the bare schema, leaving an agent without guidance on how to construct valid calls.

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 the action: 'Cancel an absence by flipping its status to cancelled'. It names the resource (absence) and the specific operation (cancel), and distinguishes it from siblings like hr_absence_list or hr_absence_record. The append-only clarification further differentiates it from delete operations.

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 clear context (cancelling an absence) and mentions the required permission (hr.manage). It does not explicitly name alternatives or exclusions, but the purpose is unambiguous enough that an agent can infer when to use this tool versus related ones like hr_absence_record or hr_absence_list.

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