get_leave_request

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

No annotations are provided, so the description must carry full behavioral disclosure. It only says 'Fetch', implying a read operation, but does not explicitly state that it is non-destructive, nor does it mention permissions, rate limits, or error behavior (e.g., invalid ID). This is insufficient for a tool with no 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?

The description is extremely concise: two lines with an Args section. Every sentence is necessary, no fluff. It front-loads the main purpose immediately.

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 that an output schema exists (not shown but indicated by context), the description does not need to explain return values. For a simple fetch tool, it covers the core functionality, parameter source, and purpose. Minor omission: no mention of error handling or non-existent IDs, but overall adequate.

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 input schema has 0% description coverage, but the tool's description explains the parameter 'request_id' as 'the numeric ID of the leave request (returned by apply_for_leave or get_leave_history)', adding valuable context beyond the schema type. This compensates for the lack of schema descriptions.

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 the tool fetches full details of a single leave request by ID, using a specific verb and resource. It distinguishes itself from siblings like get_leave_history which lists requests, and apply_for_leave which creates them.

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 mentions where to get the request ID (from apply_for_leave or get_leave_history), implying usage context. However, it does not explicitly state when to use this tool versus alternatives (e.g., get_leave_history for multiple requests) or when not to use it.

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