update_customer_address

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Update' without explaining whether the update is partial or full replacement, or what happens to fields not provided. The setAsDefault parameter's effect is also not described.

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, clear sentence that immediately states the action and target. It contains no wasted words and is easy to scan.

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 moderate complexity (nested address object, 4 params) and the absence of annotations/output schema, the description is somewhat thin. It lacks clarification on update semantics (e.g., whether all required sub-fields must be provided) but the schema covers parameter definitions adequately. The setAsDefault declaration is self-explanatory.

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 100% for top-level parameters, so the baseline is 3. The description adds no extra parameter semantics beyond the schema, but the schema already provides clear descriptions like 'Address ID to update' and 'Set as default address'.

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 uses a specific verb and resource: 'Update a customer's existing address'. It clearly distinguishes from sibling tools like create_customer_address and delete_customer_address by specifying 'existing address'.

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 clearly indicates this tool is for modifying an already-existing address. It does not explicitly name alternatives, but the context makes it obvious that this is not for creating or deleting addresses, which are covered by sibling tools.

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