reject_leave_request

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

No annotations are provided, so the description carries the full burden. It discloses that the manager_note is recommended and visible to the employee, but does not detail side effects such as notifications or status changes.

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 concise (6 lines) with a clear structure including an Args section. Every sentence adds value, though it could be slightly tighter by removing redundancy.

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?

Given the tool's simplicity and the presence of an output schema, the description covers the main behavioral context (role requirement, parameter details). It could mention that the request must be pending, but this is implied by 'pending leave request' in the first sentence.

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%, and the description adds full meaning: request_id is a numeric ID, manager_note is a reason for rejection that is recommended and visible to the employee. This compensates entirely for the schema's lack of documentation.

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 'Reject a pending leave request,' which specifies both the action (reject) and the resource (leave request). This distinguishes it from sibling tools like approve_leave_request and cancel_leave_request.

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 explicitly states 'Call this only when acting as an HR manager or team lead,' providing clear when-to-use guidance. It implies not to use as an employee, though it does not explicitly compare to alternatives like approve_leave_request.

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