Create customer

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

Annotations already declare it as a non-read-only, non-idempotent, non-destructive creation tool. The description adds useful behavior beyond those annotations: it creates an active customer with default price group, document theme, and tax settings, and it clarifies that the email is stored for quotes/invoices but no external message is sent.

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 short and front-loads the core action. However, the final sentence ('It reaches no one and stays inside Tradify') is somewhat vague and could be phrased more directly.

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?

It covers the main creation semantics and important defaults, which is valuable for a 9-parameter create tool with no output schema. It still lacks details on duplicate handling or what the tool returns, leaving meaningful gaps for an agent invoking it.

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 56%, so the schema already documents the key fields, including email and contact. The description restates email behavior and groups contact/address fields, but it adds little detail for city, phone, mobile, or postal_code, leaving several parameters without additional semantic guidance.

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 uses a specific verb and resource: it creates a new customer profile and states that the result is an active customer with company defaults. This clearly distinguishes it from list_customers and from other create_* siblings for jobs, quotes, and invoices.

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 usage by comparing it to the New Customer form and by explaining that email is used for quotes and invoices, but it does not explicitly say when to use this tool versus alternatives or when not to use it. The guidance is inferable rather than stated.

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