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

Goes well beyond annotations by disclosing that no invitation e-mail is triggered per call and that payroll/bank fields are out of scope — consequential facts not encoded anywhere else. The non-idempotency restates idempotentHint=false and it says nothing about permissions or validation failures, so it is not fully transparent.

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?

A single dense paragraph, front-loaded with the WRITE marker and the required-field contract. Every clause (idempotency, no invitation, excluded data) carries information an agent would otherwise have to guess.

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?

No output schema exists, yet the description does not say what comes back (presumably the created employee id) or how to retrieve it afterwards. Everything an agent needs to make the call correctly is present, so the gap is limited to return-value handling.

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 60%; the description compensates by mapping required fields (first name, last name, work e-mail) and naming the optional set (start date, manager, teams, position, location, phones). It omits the gender parameter entirely and adds no format or cross-reference detail beyond what the schema already provides.

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 a precise verb+resource ("add a new employee record") and immediately enumerates required vs optional fields, so the agent knows exactly what the tool produces. It is clearly distinguishable from siblings like kiwihr_update_user, kiwihr_activate_user and kiwihr_create_journey.

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?

Gives real selection context: not idempotent, no invitation sent, payroll/bank data cannot be set — so an agent knows this is the HR-record creation step only. It stops short of explicitly routing to an alternative (e.g. "use kiwihr_update_user to modify an existing employee" or "invite separately with ...").

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