job_list

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful behavior beyond that: results are scoped to dataset_root/runs/ and sorted newest-first. It does not say what happens when no jobs exist or whether results are truncated, so the addition is real but partial.

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 lines with the core behavior front-loaded and the parameter note second. No filler; the only quibble is that the parameter gloss could have been folded into the first sentence rather than a separate line.

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?

This is a simple one-parameter read tool with no output schema, so the agent needs some idea of what a job entry looks like (id, status, timestamp) and whether the list is bounded. Neither is covered, leaving a modest but real gap for a listing tool.

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 coverage is 0%, so the description must carry the parameter, and it does: dataset_root is defined as the raw-data folder path and tied to the value used in console_plan. That removes the main ambiguity for the single required parameter, though it gives no format example or path syntax.

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?

States a specific verb and resource: returns the list of jobs under dataset_root/runs/, in newest-first order. The scope and ordering are unambiguous, though it does not name a sibling (e.g. console_status) to distinguish when this list is the right source of job information.

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 explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as console_status or pipeline_status, which also expose job state. The only hint is that dataset_root matches what console_plan took, which implies the tool is used within a console workflow but doesn't state it.

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