update_customer

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

Beyond annotations (idempotentHint, openWorldHint), the description discloses that only specified fields are changed (partial update) and that the fields param controls response content. This adds valuable context not available from annotations alone.

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, 30 words total. Purpose is stated upfront, followed by two actionable tips. No redundant or filler content.

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 and nested objects, the description, combined with rich parameter schemas and annotations, gives the agent enough context to invoke the tool correctly. It covers purpose, partial update semantics, and response field selection.

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 descriptions cover all parameters (100%), so the description adds little beyond repeating the fields param purpose. The mention of 'name, email, or addresses' maps to existing parameters but doesn't provide new semantics beyond 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 customer details with specific examples (name, email, addresses), using a specific verb and resource. It distinguishes from sibling tools like create_customer and get_customer by focusing on 'Update'.

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 provides usage guidance like 'Only include fields you want to change' and 'Use fields param to request only needed fields,' but it does not explicitly compare with alternatives such as create_customer or get_customer. It implies partial update behavior but doesn't state when not to use it.

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