get_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 only says 'get details' without disclosing whether it is read-only, what happens if the leave request is not found, authentication requirements, or any side effects. The behavior is largely opaque.

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, concise sentence that states the core purpose without extraneous words. It is well-structured and front-loaded.

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?

The tool has a simple parameter set and no output schema, but the description lacks behavioral transparency and usage guidance. For a getter tool with no annotations, the description is minimal and does not adequately inform the agent about expected behavior or edge cases.

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 schema has one required parameter 'id' of type number, and the description does not explain its meaning. With 0% schema description coverage, the description should compensate but does not. The parameter's semantics are only inferable from the tool name, not explicitly stated.

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 'Obtenir les détails d'une demande de congé' clearly states a specific action (get details) on a specific resource (leave request). This distinguishes it from sibling tools like list_leave_requests (list all), create_leave_request, approve_leave_request, and refuse_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 gives no guidance on when to use this tool versus alternatives, nor any prerequisites or context. While the purpose implicitly suggests using it to retrieve details, there is no explicit mention of needing an id or when it should be preferred over listing.

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