job_list

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

The [READ] tag clearly signals a non-mutating operation, which is useful since no annotations are provided. The description also conveys that jobs are long-running operations and that results include status and duration. However, it does not disclose return structure details beyond those two fields, pagination behavior beyond limit, or error/edge-case behavior.

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?

The description is compact and front-loaded with the read intent, followed by a clean parameter list. Every line adds useful information and there is no redundant or filler text.

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?

All parameters are explained and the core purpose is clear, making the tool callable. But with no output schema and no annotations, the description only minimally describes returned fields and does not explain result ordering, required permissions, or how to route to sibling tools. The gaps are not severe for a simple read-only list, but the description is not 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?

With 0% schema description coverage, the description fully compensates by documenting all three parameters. It gives a range and default for limit, enumerates the valid status values, and explains that target comes from configuration and defaults when omitted. This is strong semantic value beyond the bare schema types.

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 identifies Engine jobs as the resource and states that the output includes status and duration. It is more specific than generic 'list jobs' and is distinguishable from sibling list tools like vm_list or host_list. The lack of an explicit 'list' verb is minor because the tool name and [READ] marker make the operation clear.

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 provides no guidance about when to use job_list instead of related tools such as event_list or undo_list. It does not state any exclusions, prerequisites, or alternative tool suggestions. An agent must infer usage context from the name alone.

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