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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by detailing the return payload, including the notable behavior that appointment times carry the company's UTC offset — a detail an agent would otherwise get wrong. It does not cover error/not-found behavior, but with annotations this is a minor gap.

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?

It is front-loaded and not bloated, but it repeats itself: the first sentence lists the sections (description, site, tasks, notes, appointments, costs, quotes, invoices) and the second sentence re-enumerates essentially the same items with more detail. Merging the two would keep all the information with less redundancy.

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?

There is no output schema, so the description rightly carries the return-shape burden, and it does so thoroughly (contact details, staff, tasks, notes, appointments with UTC offset, costs, timesheets, linked quotes/invoices). Combined with the schema and annotations, an agent has what it needs to call this correctly; only error conditions are unaddressed.

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?

There is one parameter with 100% schema description coverage ('Job ID from list_jobs'), and the description says nothing about it. Baseline 3 applies: the schema, not the prose, supplies the parameter meaning.

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 uses a specific verb-and-resource framing ('Full job... Returns one job') and immediately separates this from the list-style sibling list_jobs by stating it returns a single job. The enumeration of what a job contains (customer, site, tasks, notes, appointments, costs, timesheets, quotes, invoices) leaves no ambiguity about scope.

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?

It gives a clear when-to-use directive: 'Read it before changing a job,' which tells the agent to fetch state before mutations such as update_job_status. It doesn't name alternatives or exclusion cases (e.g. when list_jobs suffices, or how it relates to get_quote/get_invoice for linked documents), so it stops short of a full routing rule.

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