get_leave_balance

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

No annotations exist, so description carries burden. It states read-only behavior ('Check'), which is clear. However, it doesn't disclose mutability (none), required permissions, or whether balance is real-time or cached. Adequate but not detailed.

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?

One short sentence directly stating the tool's purpose with no filler. Highly efficient 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?

Tool is simple (1 param, no output schema). The description suffices for basic use, but for a balance check tool, details like output format (days? hours?) or constraints (leave types) would enhance completeness. Meets minimum viability.

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 coverage is 0% with one parameter. Description doesn't explain 'employee_id' beyond what the schema shows (employee ID). Baseline 3 is appropriate as schema is minimal, but description adds no parameter detail.

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 tool checks remaining leave days for an employee, using a specific verb ('Check') and resource ('leave days'). It distinguishes from siblings: 'apply_leave' involves submission, 'get_leave_history' shows past records.

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 use when needing current balances, but no explicit guidance on when not to use or alternatives. Given siblings, context hints (e.g., don't use for history or applying) are missing.

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