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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. What the description does add is the breadth of the returned aggregate (description, site, tasks, notes, appointments, costs, linked quotes and invoices), which is genuinely useful since no output schema exists. It stops short of covering error behavior for an unknown job_id or payload shape.

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?

Eleven words with no filler, and the field enumeration is front-loaded. The weakness is that it is a bare fragment rather than a sentence, so the most important piece of information (this retrieves one job) is implicit rather than leading.

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 single-parameter, fully annotated, read-only fetch with no output schema, listing the included sub-resources is a reasonable stand-in for describing the return value. Missing only edge-case behavior (e.g., invalid or deleted job_id) to be fully self-sufficient.

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?

Only one parameter, and the schema documents it at 100% coverage with 'Job ID from list_jobs.' With coverage this high the schema carries the semantics, so the baseline 3 applies; the description adds nothing about the ID format or constraints.

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 is a noun fragment ('Full job: ...') that enumerates the payload contents, so it does convey what the tool returns, but it never states the action (fetch a single job by ID) and relies on the name/title for the verb. It also never explicitly contrasts itself with the sibling list_jobs, so an agent must infer that this is the detail view.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as list_jobs (for scanning) or create_job/update_job_status. The closest hint, 'Job ID from list_jobs,' lives in the schema, not the description, so the description itself offers no routing information.

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