Create Job

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

With all annotation hints false, the description carries the behavioral burden. It clearly identifies this as a creation operation and adds validation context via 'Requires an exact customer name, category, and status.' Still, it does not disclose the return value, duplicate behavior, or any other side effects beyond creation.

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 with no filler. The core action is front-loaded, and the prerequisite forms a useful second sentence without adding unnecessary detail.

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?

The rich schema compensates for the short description by documenting all 13 parameters and their getter references. However, with no output schema and no positive annotation information, the description omits what the caller receives on success and gives little workflow context for a 13-parameter create operation.

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 the baseline is 3. The description adds no new parameter-level meaning: the required fields and 'exact' matching are already documented in the schema properties, so the description merely repeats what the schema already provides.

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 clear verb and resource: 'Create a new service job.' This distinguishes it from sibling read/search tools like search_jobs and get_job_details, and from other creation tools like create_customer and create_estimate.

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?

Usage is implied by 'Create a new service job' and the prerequisite of exact customer name, category, and status is stated. However, the description does not explicitly say when to choose this over alternatives, nor does it mention the getter tools referenced in the schema for satisfying exact-match values.

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