update_customer

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

With no annotations provided, the description carries the full burden. It explicitly discloses the partial update behavior ('Only provided fields are modified'), which is critical for correct invocation. It could mention return values or error handling, but the most important behavioral trait is covered.

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 two sentences with no redundancy. The first sentence states the primary purpose, and the second adds a crucial behavioral note and refers to alternatives. Every word earns its place.

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 complexity (11 parameters, no output schema), the description covers the key decision points: what the tool does, that it is a partial update, and when to use sibling tools. It could include details about the return value or required customer_id, but the schema covers the latter. Overall, it provides enough context for selection and correct invocation.

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 only 27%, so the description must compensate. The statement 'Only provided fields are modified' adds meaning to all parameters, indicating they are optional and individually updatable. While it doesn't detail each parameter, this semantic is valuable and improves over the bare 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 the tool updates an existing customer, using a specific verb and resource. It distinguishes itself from create_customer and get_customer, and also from the address management tools by explicitly directing users to add_customer_address / update_customer_address for address changes.

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 description explicitly names alternative tools (add_customer_address / update_customer_address) and states they should be used for address management, providing a clear when-not-to-use this tool. It also implies usage for updating non-address customer fields.

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