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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the mutation profile is covered structurally. The description adds two genuinely new facts beyond that: the service address is optional, and the response carries customer_id and address_id (valuable since there is no output schema). It says nothing about side effects like the notification emails the schema alludes to, or about duplicate handling given idempotentHint=false.

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?

One compact sentence with the creation scope first and the return values second; every clause carries information and there is no filler. It reads as a fragment rather than a complete statement, which slightly undercuts clarity but costs nothing in length.

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 15-parameter, all-optional create tool with no output schema, the description does the important thing by naming the returned IDs and flagging the address as optional. It still omits what an agent would want before committing a write: whether any identifying field is effectively needed, what happens on duplicate creation, and what the notification flag triggers.

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 100%, so all 15 parameters are already documented, including the homeowner/business default and the notification default. The description only contributes the grouping fact that address fields are optional; it adds no format or conditional logic beyond the schema, 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?

The description states the resource and the creation action ('New customer') and adds scope detail: an optional service address plus the identifiers returned. It is distinguishable from create_job/create_estimate by the resource noun, though it never uses an explicit verb like 'creates' and leans on the title for that.

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?

There is no when-to-use guidance, no mention of prerequisites or required permissions, and no routing to alternatives such as create_job when the intent is to schedule work. The only implicit usage hint is that the address is optional, so the agent is left to infer everything else.

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