Update Customer

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the operation is an update and defers to external docs. It does not explain partial vs. full update semantics, whether omitted fields are cleared, required permissions, validation behavior, or what the response contains.

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, front-loaded with the main action, and includes a direct documentation link. Every word earns its place without being verbose.

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 schema fully documents the two parameters and a documentation link is provided, the tool is minimally viable. However, there is no output schema and no mention of return values, error handling, or update behavior beyond the docs link, leaving meaningful gaps for an agent deciding or invoking the tool.

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% and both parameters have clear descriptions: customer_id is the Housecall Pro ID, and body is the raw JSON request body with a warning to confirm field names. The tool description itself adds little beyond the schema, so the baseline of 3 is appropriate.

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', which is a specific verb and resource. It unambiguously distinguishes this from sibling tools like create_customer, list_customers, and get_customer.

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 phrase 'Update an existing customer' provides clear context for when to use the tool. It does not explicitly mention alternatives, but the purpose is obvious given the sibling tool names and the description implicitly excludes creation and read-only operations.

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