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

Annotations already declare it as non-read-only and non-destructive; the description adds two genuinely useful behavioral facts beyond them: that no external party is notified ('reaches no one') and that it requires the user's API key with app access. It does not explain what the created record returns or duplicate-name handling.

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 opening two sentences are essentially the same sentence twice ('New customer profile, optionally with a site address' / 'Creates a customer profile, optionally with a site address'), wasting prime front-loaded space. The remaining two sentences carry real 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?

For a simple 4-parameter create tool with full schema coverage and no output schema, the description supplies purpose, auth requirement, and confirmation behavior. The only gap is any note on downstream effects (e.g., whether the new customer can then be used in quotes/invoices).

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 name/email/phone/address are all already documented in the schema. The description only echoes the optional address field and adds nothing about formats or constraints, so the baseline 3 applies.

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?

Names a specific verb and resource ('Creates a customer profile') and notes the optional site address. An agent can distinguish it from tradify_list_customers or tradify_create_job, though it never explicitly contrasts with siblings. Clever but the first sentence is a near-duplicate restatement of the second.

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 says the tool 'runs without asking first,' which is operational context, but gives no when-to-use guidance, no prerequisites beyond the API key, and names no alternative tool. An agent gets no routing signal for choosing this over other Tradify write tools.

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