apply_leave

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action and return value but does not disclose side effects (e.g., deducting leave balance, potential rejection for overlapping dates) or any constraints like minimum notice or approval requirements.

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 a compact docstring with three lines: action, parameters with examples, and return. No redundant information or unnecessary elaboration.

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-parameter tool with an output schema, the description covers the essentials. However, it lacks context about leave policies (e.g., overlapping dates, maximum days) and does not warn about potential failures, making it only marginally adequate given the absence of annotations.

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 provides only types and titles, so the description adds value by giving examples ('E004') and date format ('YYYY-MM-DD') for leave_dates. It also clarifies the return type (confirmation with remaining balance), compensating for the 0% schema coverage.

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 action ('Apply for leave') and the resource ('leave on specified dates'). It distinguishes from sibling tools like get_leave_balance and get_leave_history, which are read-only queries.

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 implies usage when an employee needs to request leave, but it does not explicitly mention checking leave balance first or compare with alternative leave-related tools. No explicit when-not-to-use guidance is provided.

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