Update client

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

Annotations already declare the write/non-idempotent/non-destructive profile, and the description adds two things they cannot: that unspecified fields are preserved, and that the client is not notified of the change. Missing only edge-case behavior such as what an empty string does, which the schema covers.

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?

Four short sentences, front-loaded with what can be changed, then how partial updates behave, then the sibling comparison. The note sentence lightly duplicates the schema's note description, so it is not perfectly waste-free.

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 6-parameter mutation with full schema coverage and no output schema, the description covers scope, partial-update semantics, sibling routing and the notification side effect. Only the response shape and permission requirements are unstated, which is a minor gap here.

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%, including removal-via-empty-string and birthday format, so the schema carries parameter meaning. The description restates the editable field list and the note-replacement rule at a high level, adding convenience but no information beyond the schema.

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 (change) and resource (a client card) plus the exact set of editable fields. It is immediately distinguishable from siblings like add_client, delete_client and add_client_note.

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?

Explicitly covers partial-update semantics ('changes only the fields given') and names the alternative add_client_note with the condition that selects it (append a line instead of replacing). It stops short of stating when not to use this tool at all, e.g. versus delete_client or find_client.

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