update_customer

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

With no annotations, the description fully discloses patch behavior ('omitted fields stay as-is'), tag replacement semantics, and uniqueness constraints. It does not cover authorization needs or error handling, but the disclosed details are sufficient for a straightforward update tool.

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 paragraph, front-loaded with the main purpose, and every sentence adds value. No redundancy or 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?

Despite no output schema, the description covers update semantics, constraints, and alternatives for related operations (tags, addresses, marketing consent). It could mention error responses or required permissions, but the provided information is sufficient for typical usage.

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 71% (5 of 7 parameters described). The description adds critical context: 'tags is a full replacement', 'omitted fields stay as-is', and uniqueness constraints for email/phone. The term 'name' in the description could be ambiguous (firstName/lastName), but the schema clarifies. Overall, it adds value 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 customer's profile fields' and lists specific fields (email, name, phone, tags, internal note). It distinguishes from sibling tools like add_tags/remove_tags and address-specific mutations, establishing a clear scope.

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 tells when to use this tool (for updating profile fields) and when to use alternatives: add_tags/remove_tags for additive/subtractive tag changes, address-specific mutations for addresses, and customerEmailMarketingConsentUpdate for marketing consent. Also notes uniqueness constraints for email/phone.

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