Create Customer

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

The permission note adds context beyond annotations, which already indicate readOnlyHint=false and destructiveHint=false. It does not contradict annotations and provides useful behavioral info about potential authorization failures.

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?

Extremely concise: two sentences that deliver the core purpose and a critical caveat. Every word earns its place, with no redundancy or filler.

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 is adequate for a create operation with 14 parameters and good schema coverage, but misses a note on the return value or response structure (no output schema provided). The permission guidance partially compensates.

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 descriptive parameter names and brief descriptions. The description does not add additional parameter meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description clearly states the action ('Create a new customer record') and the resource ('in Service Fusion'). It directly conveys the tool's purpose with a specific verb and resource, distinguishing it from sibling tools like search_customers or 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?

Provides explicit guidance on permissions ('may require elevated API permissions') and a fallback action if a 403 error occurs ('customer creation must be done through the Service Fusion web UI'). This helps the agent know when the tool is viable and what to do otherwise.

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