update_customer_payment_method

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

With no annotations, the description conveys the request method (PUT), scope (only billing address), and gateway-agnostic nature. Additional side effects or error conditions are not described, but this is sufficient for a simple update.

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, no redundancy, key information front-loaded with action and resource, then details and constraints.

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?

Missing description of return values (no output schema) and potential errors or idempotency. However, the tool is straightforward and the description covers essential usage aspects.

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%, so baseline is 3. The description adds context beyond schema by explaining the purpose of each parameter and emphasizing that no gateway fields are involved, improving understandability.

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?

Explicitly states 'Update a payment method's billing address (gateway-agnostic)', specifying both the action and resource, and distinguishes from sibling tools like create_customer_payment_method.

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?

Clearly indicates when to use (update billing address) and lists required and optional fields. Includes constraints like 'No payment or gateway-specific fields', but lacks explicit when-not-to-use or alternatives.

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