clokio_create_employee

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

Discloses behavioral nuances beyond the annotations: reactivation preserves the existing password, pins are 4-6 digits and org-unique, and the pin is only returned at creation time. Given that annotations only provide readOnlyHint=false and destructiveHint=false, the description adds meaningful safety-relevant 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?

Two dense, front-loaded sentences with no filler or redundancy. Every sentence earns its place, and the most important behavioral caveats come early.

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?

Captures the critical reactivation edge case and pin lifecycle, which are essential for correct invocation. However, with no output schema, it does not describe what the response contains beyond the pin, and it leaves unclear what happens if an active employee with the same name or email already exists.

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 must compensate for undocumented parameters. It explains the pin parameter well (format, uniqueness, auto-generation) but says nothing about name, email, phone, or location_id, leaving most parameters underspecified.

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?

States specific verbs 'create (or reactivate)' and a clear resource, 'an employee.' The reactivation framing distinguishes it from sibling employee-focused tools like clokio_set_employee_status and clokio_lookup_employee.

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?

Provides clear context that the tool can be used both for new employees and for reactivating inactive employees, with the important caveat that reactivation does not reset passwords. It does not explicitly name alternatives or say when not to use the tool, but the usage context is clear.

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