get_employee_leave_balance

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

With no annotations, the description carries the full burden. It discloses a return type ('Leave balance message') but does not explain the message content, confirm it is a read-only operation, or mention any potential side effects or limitations. The term 'message' is vague.

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 concise and uses a structured docstring format, but it is under-specified. While not bloated, a few additional words could significantly improve clarity without sacrificing conciseness.

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?

Even for a simple tool, the description omits critical context such as what the leave balance message contains, error scenarios (e.g., invalid employee ID), and how this tool relates to get_leave_history. The output schema exists but is not referenced, and the description adds little supplementary value.

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 description's ':param emp_id: Employee ID' merely repeats the parameter name and schema title. It adds no format, example, or contextual meaning beyond the schema's type and required flag. With schema description coverage at 0%, the description fails to compensate.

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 'Get the leave balance of an employee' with a specific verb and resource. It distinguishes from sibling tools like get_leave_history and get_employee_details by focusing on 'balance' and the employee relationship.

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?

No guidance is provided on when to use this tool versus alternatives such as get_leave_history or apply_leave. There are no use case descriptions or exclusions.

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