Create Customer

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

Beyond the annotations, the description reveals a real API limitation: Service Fusion publishes no item schema for contacts/locations. It also interprets 403 responses as a credential-permission problem. These details help the agent react correctly to failures and avoid wasted calls.

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 three focused sentences, each carrying distinct information: the action, unsupported fields with the alternative, and the 403 error interpretation. There is no filler, repetition, or irrelevant detail.

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 simple create operation with one required parameter and no nested objects, the description covers the essential calling context, limitations, and error behavior. It does not describe the success response shape, but the absence of an output schema and the simplicity of the tool keep this gap minor.

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 the schema already documents all three parameters and their constraints. The description does not add parameter-specific meaning, such as allowed formats or relationships between parameters. The note about contacts/locations is useful context but does not map to any parameter in 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 states the specific verb and resource: 'Create a new customer record.' It also clarifies what cannot be done (contacts/locations), which distinguishes this tool's scope from broader customer-management operations. This makes it easy to tell apart from sibling tools like create_job and create_estimate.

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 explicitly says when not to use this tool: contacts/locations cannot be set here and must be added via the web UI. It also explains the 403 error condition and directs the agent to use the web UI when credentials lack permission. This is clear, practical guidance with alternatives.

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