Create Customer

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

The description adds 'All fields are optional,' but this information is already evident from the schema (0 required parameters). With annotations already indicating a write operation (readOnlyHint=false), the description offers no additional behavioral context such as return value, side effects, or authentication needs. The openWorldHint=true annotation hints at external implications, but the description does not elaborate.

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, efficient sentence that includes the HTTP method and path. It is front-loaded with the core action and contains no fluff.

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?

For a create operation with 11 parameters, nested objects, and no output schema, the description is too sparse. It does not indicate what a successful response returns, possible error conditions, or any constraints or side effects. The openWorldHint annotation suggests broader implications, yet the description stays silent.

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% with detailed descriptions for all 11 parameters, so the description need not repeat them. The statement that all fields are optional aligns with the schema's lack of required fields, but does not add new meaning beyond the 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 'Create a new customer' with the explicit endpoint 'POST /api/customers', identifying the verb and resource distinctly. This naturally differentiates it from siblings like gorgias_update_customer and gorgias_delete_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?

No guidance is provided on when to use this tool versus alternatives. It does not clarify prerequisites, such as whether an external_id is required for integration, or when updating an existing customer would be preferable. The only usage clue is the obvious 'create' action.

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