Create Customer

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

The description adds specific behavioral context beyond the openWorldHint annotation by explicitly stating it stores PII and exists for reuse across payments. This clarifies the persistence side effect, though it could mention data retention, security, or idempotency, but with the annotation covering general side effects, the added detail is valuable.

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, concise sentence that front-loads the action and purpose. It contains no filler or redundant information.

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?

The description and schema together cover the tool's inputs and basic purpose, but with no output schema, the description does not mention what the tool returns (e.g., customer ID or object). It also lacks guidance on edge cases or prerequisites, making it minimally adequate.

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%, so the parameters are already well-documented in the schema. The description adds no additional parameter-specific meaning, aligning with the baseline of 3.

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 a specific action (create) and resource (customer record), and adds purpose ('stores PII for reuse across payments'). This distinguishes it from sibling tools like create_payment or create_payment_method, which create other entities.

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 implies when to use this tool through 'stores PII for reuse across payments,' suggesting it's for storing customer data for future transactions. However, it does not explicitly state when not to use it or mention alternatives, such as create_payment_method for non-PII payment details.

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