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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces rather than merely repeats them by explaining why: the tool 'opens nothing by itself' and only returns instructions, which resolves the tension between the name 'create_job' and a read-only safety profile. It adds the required follow-up execution path via cotlet_browser_* but does not describe the shape or length of the returned guide.

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 core action and the handoff are front-loaded, which is good, but the final sentence about Service Fusion's Open API being Pro-plan-only and having no official MCP server (with a dated 'checked 11 Oct 2026' note) is vendor trivia that does not change how an agent invokes this tool. The middle sentence is also a dense semicolon-joined run-on that mixes the return value with the follow-up instruction.

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?

With no parameters and no output schema, the description carries the burden of describing the return value, and it does: a step-by-step procedure covering screens, buttons and fields, plus the instruction to execute it with the browser tools. What it omits is failure or prerequisite handling, such as what to do when the user lacks a connected Service Fusion session.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the schema is empty with additionalProperties false and coverage is 100%. Baseline for a no-parameter tool is 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 states a specific verb-and-resource outcome: it returns a step-by-step how-to (screens, buttons, fields) for creating a job in the user's own Service Fusion account, and explicitly 'opens nothing by itself.' That distinguishes it from the sibling cotlet_browser_* tools, which perform the actual UI actions. It does not explicitly differentiate itself from service_fusion_create_estimate or service_fusion_create_invoice, so it stops short of a 5.

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?

The workflow is spelled out: call this first to get the procedure, 'then do it with the cotlet_browser_* tools in the user's Service Fusion Cloud Browser.' That is a clear when-to-use and an explicit handoff to the alternative tool family. It lacks explicit when-not-to-use conditions (e.g. what to do if no Service Fusion account is connected).

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