get_leave_balance

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

No annotations are provided, so the description must convey behavioral traits. It only implies a read-only operation ('check') but omits details like permissions, side effects (e.g., whether the operation is logged), or the format of the result. With output schema existing, the return format is covered, but the description itself adds minimal transparency.

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, front-loaded sentence of 8 words. Every word contributes to the purpose, and there is no redundancy or filler. Ideal conciseness for a simple tool.

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?

Given the tool's low complexity (one parameter, output schema exists), the description is functionally adequate but lacks context such as what specific leave-related data is returned (e.g., total, used, or remaining days) and when to prefer this over siblings. Output schema may fill some gaps, but the description alone leaves room for interpretation.

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 only parameter 'employee_id' has no schema description (0% coverage) and the tool description merely says 'for the employee', offering no additional semantics about expected format, domain, or validation. The description does not compensate for the missing parameter documentation.

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 ('Check') and the resource ('how many leave days are left for the employee'), making the tool's purpose unambiguous. It also naturally distinguishes from sibling tools 'apply_leave' (applies leave) and 'get_leave_history' (retrieves history) by focusing on balance.

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 explicit guidance is given on when to use this tool versus its siblings. The description implies checking current balance but does not explain that 'get_leave_history' is for past usage or that 'apply_leave' is for deductions. This leaves the agent without decision criteria.

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