kaiten_update_sd_user

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the mutating verb 'Update' without explaining whether the operation is a partial patch or full replacement, what permissions are required, or what side effects occur.

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 a single focused sentence with no filler and is front-loaded with the action. It is concise, though slightly terse and does not use its brevity to add distinguishing detail.

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?

For a mutating tool with no annotations, no output schema, and many closely related update tools, a one-line description is insufficient for reliable selection and invocation. It omits when to use it, what qualifies as a Service Desk user, and any behavioral caveats, though the flat parameter list and full schema coverage keep the gap moderate.

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 user_id, lng, and full_name are already documented. The description adds no additional parameter-level meaning, which is acceptable given that the schema fully covers the parameters.

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 uses a specific verb ('Update') and a specific resource ('Service Desk user profile'), making the basic action clear. However, it does not differentiate this tool from closely related siblings such as kaiten_update_sd_org_user or kaiten_update_space_user.

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?

There is no guidance on when to use this tool versus alternatives like kaiten_update_sd_org_user, kaiten_update_space_user, or kaiten_set_sd_user_temp_password. No context, prerequisites, or exclusions are provided, so the agent must infer usage from the tool name alone.

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