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

Annotations already declare readOnlyHint=true, so safety is covered; the description goes further by disclosing the returned field set and, notably, that the response carries the version required for subsequent updates — a real concurrency/optimistic-locking signal. It stops short of stating auth needs, error behavior, or whether the version goes stale.

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?

One dense, front-loaded sentence that puts the action first, followed by the API path reference. Efficient, though the trailing 'Sortly: GET /api/v1/jobs/{job_id}' is largely restating what the name and schema already convey.

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?

No output schema exists, so the description must carry return-value information — and it does, listing the fields the agent can expect. Combined with the read-only annotation and the single well-documented parameter, nothing essential is missing for correct invocation.

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?

One required parameter at 100% schema coverage, so the baseline is 3. The description adds only indirect meaning to folder_id (where pulled items sit) and says nothing about job_id beyond what the schema already states ('The job's id', positive integer).

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?

Specific verb ('Fetch a single job') plus an enumeration of the payload's contents (status, folder_id, dates, notes, custom field values, version), which cleanly separates it from the sibling list_jobs and the create/update/move job tools. An agent can identify the tool without opening the schema.

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?

Usage is implied rather than stated: the mention of 'the version needed for updates' hints this precedes an update call, but no explicit when-to-use condition, prerequisites, or named alternative (e.g., list_jobs for enumeration) is given. Adequate but leaves routing to inference.

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