apply_leave

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

With no annotations, the description provides no behavioral context beyond the action itself. It does not disclose side effects, whether approval is required, how conflicts are handled, or permissions needed. The only extra is the date array example.

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 single sentence with a concrete example, front-loaded with the verb, and contains no redundant information.

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-required-parameter mutation tool, the description omits the employee_id parameter entirely and gives no information about constraints or process. Although an output schema exists, the description does not fully compensate for the 0% schema description coverage.

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%. The description adds meaning only to leave_dates via an example, but leaves employee_id entirely unexplained beyond its property name. No additional semantics for employee_id are provided.

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 uses a specific verb ('apply') and resource ('leave'), and the example clarifies the expected date array format. It is clearly distinct from the read-only siblings (get_leave_balance, get_leave_history).

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 for requesting time off but does not explicitly state when to use this versus the sibling getter tools, nor any prerequisites or exclusion criteria. The contrast is implicit through the tool name and sibling names.

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