get_leave_history

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

No annotations provided, so description must fully disclose behavior. It only says it returns a 'Leave history message' with no detail on format, content, or side effects (e.g., mutation, auth requirements). Minimal 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?

Short but includes redundant docstring-style parameter documentation after the purpose statement. Could be more front-loaded and eliminate the param line since the schema already defines emp_id.

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?

Despite presence of an output schema, the description is incomplete. Lacks usage guidance, behavioral details, and parameter semantics. Does not inform the agent about what constitutes valid input or expected output beyond a vague 'message'.

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%, so description must add value. It only restates the parameter name and type (':param emp_id: Employee ID'), essentially duplicating the schema. No additional meaning like format, constraints, or examples.

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?

Clearly states 'Get the leave history of an employee', using a specific verb and resource. Distinguishes from siblings like get_employee_leave_balance (balance vs history) and apply_leave (application vs retrieval).

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 on when to use this tool versus alternatives. Does not state prerequisites or contexts where it should or should not be used. The description only states what it does, not when or when not.

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