hr_live_leave_balance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only operation but does not explicitly state that it is non-destructive, specify authentication requirements, rate limits, or what data is included (e.g., pending leave adjustments). The description lacks sufficient behavioral context.

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 very short (one sentence) and thus concise, but it lacks structure and detail. It front-loads the key information but could benefit from additional context about the purpose and scope. It is not verbose, but it is also not optimally informative.

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 simplicity (one parameter, clear purpose) and the presence of an output schema, the description is partially complete. However, it does not explain what the balance value represents (e.g., accrued, available, remaining), whether it includes pending leave, or the time period. An agent might need to infer from the output schema.

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 0%, and the description does not explain the 'bamboo_employee_id' parameter beyond its schema title. While the parameter is self-explanatory as an employee identifier, the description adds no additional meaning, such as how to find the ID or its format. The schema itself provides minimal context.

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 'BambooHR leave balance for an employee' clearly identifies the resource (leave balance) and the implied action (retrieve/view). It distinguishes itself from sibling tools like 'hr_live_whos_out' (who is out on leave) and 'hr_leave_request' (requesting leave) by focusing specifically on the current 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or exclusion criteria. Agents have no information about scenarios where this tool is appropriate or when another tool (e.g., hr_live_whos_out) should be used instead.

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