Delete a temporary absence

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

Annotations already mark this as destructive and non-read-only, so the description's added value is the side-effect warning that recipients may be notified and tenant data may change, plus the write-opt-in requirement. This goes beyond the structured annotations without contradicting them.

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?

Three short sentences convey endpoint, body expectation, reference, prerequisites, and side effects with little waste. Minor double spacing and a reference URL are acceptable; info is front-loaded and scannable.

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 two-required-parameter delete with no output schema, the description covers the endpoint, required confirmation, opt-in, body expectation, and side effects. A response/status-code note would be a small improvement, but nothing essential to invoking it correctly is missing.

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?

The schema already documents query and confirm in detail, and the description adds only 'Body fields: none' and the path variable name through the endpoint. The temporaryAbsenceId parameter has no explicit prose description but is self-explanatory from the endpoint; the added value over the schema is modest.

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 states a specific action ('Delete a temporary absence') and gives the exact REST endpoint, which unambiguously identifies the resource and operation. This distinguishes it from the sibling create/get temporary-absence tools even without inspecting the schema.

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 provides clear invocation context by stating the DELETE verb, that no body fields are needed, and that operator write opt-in plus confirm:true are required. It doesn't name alternatives or exclusions, but for a deletion operation the trigger condition ('delete a temporary absence') is sufficiently clear.

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