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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context by saying the result is a draft and that no client communication occurs, but it says nothing about validation failures, what the required idempotencyKey does, or whether the draft is subsequently editable.

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?

Two short sentences, front-loaded with the operation and followed by the key behavioral caveat; no filler. It is efficient, though the terseness is part of why parameter semantics go uncovered.

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?

An output schema exists so return values need not be explained, but for an 8-parameter creation tool with zero schema descriptions the definition is too thin. Nothing explains idempotencyKey, required-field expectations, or what happens on a duplicate submission.

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 0% across 8 parameters, including four required ones, and the description compensates for none of it. Critical semantics such as the purpose and replay behavior of idempotencyKey, or expected format of jobType and clientName, are left entirely undocumented.

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 a specific verb ('Creates') and a specific resource ('owned job draft'), which distinguishes it from sibling draft creators like create_invoice_draft and create_quote_draft by resource type. It stops short of explicitly contrasting itself with those siblings, but the resource name is unambiguous.

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, and no routing to alternatives such as create_invoice_draft or save_estimate_draft. 'This does not contact the client' clarifies side effects rather than when to choose this tool.

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