Job List

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

The readOnlyHint annotation already indicates this is read-only, and the description aligns with that (listing does not modify state). However, no additional behavioral context is provided, such as how results are ordered, paginated, or what happens when status is omitted.

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 a single concise sentence that communicates the core purpose without unnecessary words or structure.

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?

The description provides enough for a high-level understanding but lacks details about the optional status filter, the exact structure of the returned list (beyond 'states'), and any response size or pagination behavior. Given the low complexity and presence of a read-only annotation, it is minimally complete but not thorough.

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 only parameter, 'status', has no description in the schema or the tool description. Its meaning, possible values, and filtering behavior are entirely unexplained, leaving an agent to guess how it affects the result.

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 clearly states the action (list) and the resource (background scans) and mentions the output includes states. It is distinct from other siblings like job_fetch or job_status, though it does not explicitly name alternatives or specify whether it lists all or requires filtering.

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?

No usage guidance is provided. The description does not indicate when to use this tool over sibling list/fetch tools, nor does it mention any prerequisites or common scenarios.

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