create_leave_request

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'create a leave request' with no information about side effects, validation, approval flow, or potential errors. This is a bare tautology that adds no behavioral insight.

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 short, but this is under-specification rather than efficient conciseness. A single phrase doesn't provide adequate information for an agent to understand the tool's function or usage. It earns no credit for compactness because it omits essential content.

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 creation tool with 7 parameters and no output schema, this description is entirely insufficient. It fails to explain the effects, required fields, or typical usage scenario. The agent would need external knowledge to invoke it correctly.

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 86%, so most parameters already have descriptions. The tool description adds no parameter details beyond the schema, but the baseline of 3 applies because the schema carries the load adequately.

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 'Créer une demande de congé' clearly states a specific verb (create) and resource (leave request), distinguishing it from sibling tools like list_leave_requests or approve_leave_request. Even though it's short, it unambiguously conveys the action and object.

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?

There is no guidance on when to use this tool versus alternatives. The description simply restates the action without context, exclusions, or references to related tools. No mention of prerequisites like employee existence or validation workflows.

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