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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the external side effect (an email is sent to the employee), the re-invocation/re-send semantics, the address-update behavior, and the hard failure mode for already-accepted employees. The user-confirmation requirement is extra operational guidance not in the annotations.

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?

Three tight sentences: the write/email warning is front-loaded, then the mechanism, then the re-invocation and failure rules, ending with the confirmation instruction. No sentence is filler.

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?

With only 3 parameters, full schema coverage, no output schema, and annotations covering safety, the description supplies everything an agent needs: side effects, preconditions, re-send semantics, and the confirmation requirement.

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 100%, so id, inviter_user_id, and crew_input_form_id are already documented in the schema. The description only restates the email requirement already present in the id parameter's description, adding no syntax or format detail. Baseline 3 applies.

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 specific verb and resource ('Invite an employee to SmartHR') and explains the mechanism (an email with a login-creation and data-entry form). This clearly distinguishes it from smarthr_create_employee, which creates the record rather than inviting the person.

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 concrete conditions: employee must have an email, re-calling re-sends the invitation and updates the address, and already-accepted employees cannot be re-invited. It also mandates confirming with the user first. It never names a sibling alternative explicitly, so it falls short of a 5.

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