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

Annotations already mark this as non-read-only and open-world, but the description adds real context: the default confirmation gate, the ability to switch it off, and the auth requirement for the user's Cotlet API key. The note that a Canceled change impacts a customer's contract is useful impact disclosure, though it sits in mild tension with destructiveHint=false.

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 text repeats itself: the Job/Contract Status change is stated twice, and confirmation is covered three times ("the call asks first", "confirm each call", "confirm with the user before each call"). Tighter editing would preserve all the content in roughly half the space.

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 3-parameter mutation with no output schema and full schema coverage, the description supplies the missing pieces an agent needs: auth requirement, confirmation behavior, and the customer-contract impact. Only the absence of any return-feedback expectation keeps it from being fully complete.

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 coverage is 100%, so job_id, job_status and contract_status are already documented. The description adds only that you can set the statuses to values "from your own lists" and change either or both at once, which is marginal value beyond the schema's own wording.

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?

States a specific verb and resource: "Change a job's Job Status or Contract Status, for example to Canceled." It is clearly distinguishable from read siblings such as marketsharp_get_job and marketsharp_list_jobs, and it names the two addressable fields explicitly.

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?

Gives a concrete use case (e.g. moving to Canceled) and flags the operational context that the call prompts for confirmation, which you can disable. It does not name alternative tools (e.g. marketsharp_get_job to read first) or state when not to use it, so it stops short of full routing guidance.

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