updateCustomers

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

Annotations indicate destructive, idempotent, and open world hints. The description adds behavioral details: partial patch (only included keys replaced) and scope (both members and non-members). No contradiction with annotations. The additional context is valuable but not exhaustive.

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 in Japanese, front-loaded with the main action, then provides behavioral details and sibling references. Every sentence earns its place with no wasted words.

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 no output schema, the description lacks explicit return value information. However, it covers the key behavioral aspect (partial update) and references related tools for other operations. Adequate for a patch tool with good annotations.

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?

The input schema has descriptions for all parameters (though context says 50% coverage, the provided schema shows 100%). The description adds that customer_id identifies the target and only keys in 'customer' are replaced, but this is already implied by the schema structure. Minimal additional meaning 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 the tool applies a partial patch to customer attributes, specifying the resource (existing customers, members and non-members) and the action (differential update). It also distinguishes from sibling tools like updateCustomerMembership and postCustomerPoints.

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 provides when to use this tool (for attribute updates) and when to use alternatives: membership rank changes -> updateCustomerMembership, point balance changes -> postCustomerPoints, viewing -> getCustomer, searching -> getCustomers. It also clarifies that only provided keys are updated, guiding correct usage.

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