Reject Leave Request

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

Adds context beyond annotations: 'TRUST AREA — HR DECISION' signals permission level, and labor-law compliance emphasizes regulatory implications. Annotations confirm idempotentHint=true, and description aligns by noting reason is mandatory for each rejection. No contradictions.

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?

Extremely concise: two sentences in English followed by Spanish translation. Front-loaded with trust area and purpose. No fluff.

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?

Simple tool with 2 required params and output schema. Description covers purpose, mandatory nature of reason, and compliance context. Could briefly state that only pending requests can be rejected, but implied by 'pending leave request'.

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 coverage is 100% and both parameters have clear descriptions. The description merely reiterates that reason is mandatory, adding minimal value beyond schema.

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 the verb 'Reject' and the specific resource 'pending leave request'. Distinguishes from siblings like leave_approve, leave_cancel, and leave_request_create by emphasizing rejection with mandatory reason.

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?

Indicates 'TRUST AREA — HR DECISION' suggesting HR role, but does not explicitly state when to use versus alternatives like leave_cancel or leave_approve. No exclusions or when-not scenarios provided.

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