hr_offboard

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

With no annotations, the description must disclose behavioral traits. It lists actions but does not detail side effects, permission requirements, reversibility, or what gets destroyed. The added value is minimal.

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 (2 sentences plus parameter list) and front-loads the purpose. The parameter list adds detail but is slightly verbose. Overall efficient.

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?

The tool has 4 params and an output schema (not shown). The description does not mention return values, side effects, or error conditions. Given the complexity of offboarding, more context is needed for safe invocation.

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 the description should compensate. The Args section provides some context but incorrectly states employee_id as required (schema says optional). Other params have minimal explanation; voluntary is not described. This contradiction with schema reduces reliability.

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 starts with 'Run employee offboarding' and lists specific operations (revoke access, transfer ownership, etc.), clearly stating the action and resource. It distinguishes from sibling tools like hr_onboard and hr_leave_request.

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 when to use (offboarding) but does not explicitly state conditions, prerequisites, or alternatives like the hr_employee_offboarding_loop sibling. No mention of when not to use.

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