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

readOnlyHint=true and openWorldHint=false already establish this as a safe, non-open-world read, so the bar is low. The description usefully adds that results are ordered newest first, but omits pagination behavior, default result count, and what 'recent' means, which matter for a list tool.

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?

A single short fragment with the ordering constraint front-loaded and no filler. It is efficient, though the terseness borders on under-specification rather than tight communication.

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?

With no output schema, no annotation detail beyond safety hints, and an undocumented limit parameter, the description leaves an agent without the pagination/default-count information needed to call this list tool predictably. It is too thin for the tool's surface.

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?

The lone parameter 'limit' has 0% schema description coverage, so the description must carry its meaning, but it says nothing about the limit, its allowed range (1-50), or a default. It mentions 'recent' without defining the window, leaving the retrieval size entirely undocumented.

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 fragment identifies the resource (the account's jobs) and its ordering (newest first), so an agent can guess it retrieves a job list. But there is no verb and no differentiation from siblings get_job, get_job_results, or list_pipelines, which are equally plausible for a job-related need.

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?

The description gives no indication of when to call this versus get_job (single job) or get_job_results (results of one job). No prerequisites, no conditions, no exclusions are stated.

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