Create Job

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

Description mentions it is a creation operation (consistent with annotations) and specifies that it returns the job record with its assigned number. It adds context about required exact matches. Annotations already indicate non-readOnly and non-destructive, so description adds value. Could be improved by noting any side effects or permissions, but currently sufficient.

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?

Three sentences with no fluff. The first sentence states the purpose, the second lists essential prerequisites, and the third describes the return value. Well-structured and efficient.

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?

Given the complexity of 19 parameters and full schema coverage, the description provides sufficient context for core functionality: required params, usage hints, and return value. It could mention error handling or validation, but remains complete for typical use. No output schema reduces the need to explain return format.

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 extra guidance for required parameters (e.g., using search_customers for customer_name, listing common category and status values). This provides additional context beyond the schema definitions, justifying a 4.

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 clearly states it creates a new service job in Service Fusion and returns the created record with an assigned job number. It distinguishes itself from sibling tools like create_customer and create_estimate by specifying the domain (service job).

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?

Provides explicit guidance: requires exact customer name (referencing search_customers), category (referencing get_job_categories with examples), and status (referencing get_job_statuses with examples). This helps the agent select and invoke the tool correctly.

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