list_jobs

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

No annotations provided, so the description must fully convey behavioral traits. It mentions 'recent' but does not define recency (e.g., time window) nor indicate read-only nature or any side effects. Missing critical context for safe invocation.

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?

Extremely concise with a single sentence that communicates the core purpose. No wasteful repetition, but could be improved by front-loading critical context like return type.

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?

Given a simple tool with one optional parameter and no output schema, the description should at least hint at the response format (e.g., list of job IDs/statuses) or default ordering, but it does not. Incomplete for an agent to fully understand what the tool returns.

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?

Only one parameter (limit) is present, fully defined in the schema with default, min, max. The description adds no additional meaning beyond the schema, but schema coverage is 100% for that parameter, so baseline of 3 is appropriate.

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?

Description clearly states the tool lists Lightroom Classic jobs, with a specific verb and resource. However, it does not differentiate from sibling tools like job_status or job_error, which may also list jobs with different scopes.

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 guidance on when to use this tool versus alternatives. Siblings include cancel_job, job_error, job_result, job_status, etc., but the description does not explain that this list is for recent jobs or how it differs from job_status.

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