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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the safety profile is partially covered; the description adds real value on top by disclosing the default Pending status, the approve-absence permission gate for Approved, the required Basic plan, and the side effect that hours are derived from Shiftbase's expected-hours calculation. It adds no contradiction with the annotations.

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?

Four compact sentences with the operation class and resource front-loaded, no filler, and the endpoint last. Dense but each sentence carries distinct information (status semantics, permission, hours source, plan requirement).

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 7-parameter write tool with no output schema, the description covers the mutation semantics, permission/plan prerequisites, side effects, and the reference sibling for absence types. It does not describe what is returned (e.g., the created absence id) or what destructiveHint implies for existing bookings, which is a minor residual gap.

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 schema already documents all 7 parameters including the status enum, date patterns, and the absence_type_id cross-reference. The description mostly restates the status semantics the schema already states, adding only the behavioral note about how per-day hours are computed, so baseline 3 is appropriate.

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?

Starts with an explicit operation class (WRITE) plus a specific verb and resource: 'add an absence (leave/time-off request) for an employee', and closes with the concrete endpoint POST /absentees. This clearly separates it from read siblings like shiftbase_get_absence / shiftbase_list_absences and from shiftbase_review_absence.

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 explains the two operating modes (default Pending vs Approved booking directly) and the permission required for the Approved path, plus a plan prerequisite (Basic plan). It does not explicitly state when to prefer this over shiftbase_review_absence or shiftbase_update_* flows, so it falls short of full when/when-not routing.

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