Delete A Time Off Record

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

Annotations already declare destructiveHint=true, so description adds value by emphasizing irrevocability and stating the returned ID. No contradictions with 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?

Slightly repetitive: 'This cannot be undone' appears twice, and 'Permanently removes' is stated twice. Still front-loaded with main action, but could be more concise.

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?

Describes what is returned (ID), mentions required parameters, and specifies the API endpoint. For a delete tool with no output schema, this is fairly complete, though it lacks error conditions or prerequisites.

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 baseline 3. Description lists required parameters but adds little beyond the schema. Provides endpoint URL, which indirectly clarifies parameter roles as path parameters.

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?

Clearly states it deletes a Time Off record for a specified person within a company, with specific verb 'Deletes' and resource identified. Distinguishes from siblings like get_single_time_off_record and update_a_time_off_record via the delete 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?

Explicitly says 'Use this to permanently delete' but does not provide when-not-to-use or alternative tools. However, context implies deletion is for permanent removal, and siblings include update and get for non-deletion actions.

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