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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful context beyond that: the underlying endpoint (GET /v1/jobs) and the important caveat that a call returns one page rather than all matching records, which changes how an agent must loop with pageIndex.

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?

Two short sentences, front-loaded with what is returned and followed by the paging caveat – no filler. The first sentence is a noun fragment rather than a clause, which makes it slightly less scannable than it could be.

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 6-parameter list tool with no output schema, the definition covers returned fields and the paging constraint but leaves open how to retrieve a full result set and how filters combine. The rich schema compensates substantially, keeping this at minimum-viable rather than inadequate.

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 description coverage is 100%, so every parameter (limit, fields, wField/wValue, pageIndex, wOperator) is already documented with defaults and constraints. The description adds no parameter-level detail such as filter syntax or default page size, so baseline 3 applies.

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 names the resource (jobs) and the fields returned (account/order/route IDs, estimated times, status), so the agent knows exactly what comes back. It stops short of distinguishing this from siblings like list_order_jobs or list_job_timelogs, which list subsets of the same records.

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 guidance on when to use this versus alternatives such as list_order_jobs (jobs for one order) or get_job (single record). The only usage-adjacent statement is the pagination caveat, which is about mechanics rather than tool selection.

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