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

Beyond the annotations (readOnlyHint false, destructiveHint false, openWorldHint true), it discloses several non-obvious behaviors: the customer may receive an outbound email if Email Settings are enabled, the default per-call confirmation can be disabled for this tool, the call reaches other people, and a Cotlet API key with app access is required. This is exactly the side-effect/auth context annotations cannot carry.

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 purpose is front-loaded, but the opening two sentences overlap ('New job for a customer, scheduled or unscheduled' vs 'Creates a job under an existing customer'), and the confirmation guidance is split awkwardly across two sentences. Some trimming would improve it.

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 mutation tool with seven parameters and no output schema, the description covers the important service-fusion-specific behaviors: scheduling semantics, email side effect, confirmation requirement, and auth needs. It could say more about the return value, but overall it is sufficient for correct invocation.

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 every parameter is already documented. The description's only added semantics is the Scheduled/Unscheduled rule tied to 'start' and 'techs_assigned', which largely restates the schema's own 'Empty: Unscheduled' note. 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?

The description gives a specific verb and resource ('Creates a job under an existing customer') and clearly scopes it to customers that already exist. It does not, however, name or distinguish itself from the most relevant sibling, convert_estimate_to_job, so an agent must infer the boundary. Purpose is unambiguous but sibling differentiation is absent.

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?

It supplies real usage context: whether to pass 'start' and 'techs_assigned' determines Scheduled vs Unscheduled, and it warns to confirm with the user before each call. No explicit when-not guidance or named alternative is provided, so it stops short of a 5.

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