lexware_update_contactUpdate an existing contact in Lexware Office. Provide the contact ID and JSON body with the version field to ensure optimistic locking.
Update an existing contact. The body must include the version field for optimistic locking.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Contact ID | |
| body | Yes | Contact JSON with version field. Same structure as create. |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses optimistic locking via version field, which is beyond annotations. No contradictions; adds meaningful behavioral context despite annotations already present.
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 sentences with no waste. The first sentence states purpose, the second adds the critical requirement. Ideal length.
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?
Given the tool's simplicity, annotations, and schema coverage, the description is largely sufficient. Lacks details on constraints or typical usage flow, but within acceptable bounds.
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 100% with descriptions. The description adds emphasis on the version field requirement, providing extra clarity 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?
The description clearly states 'Update an existing contact', specifying the verb and resource. It distinguishes from sibling tools like create or get contacts.
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?
The context is clear for updating a contact, but no explicit when-not or alternative guidance is provided. The requirement for the version field implies needing to fetch first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.