remote_job_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether this is a read-only operation, what the default behavior is (e.g., listing all jobs vs. only a session), or whether pagination or ordering applies. The phrase 'optionally restricted to one session' hints at filtering but does not explain default 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 a single, front-loaded sentence of nine words. It wastes no words and clearly states the primary action and the optional modifier.

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 tool is simple (one optional parameter, likely a list output) and an output schema exists, so the description does not need to detail return values. However, it lacks usage guidelines and behavioral details like default behavior or read-only status, making it minimally viable but not fully complete.

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 schema has zero description coverage, but the description does give some meaning to the session_name parameter by stating that the list can be 'restricted to one session.' However, it does not clarify the format or whether it refers to a session ID or name, leaving room for ambiguity.

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 uses a specific verb 'List' with a clear resource 'asynchronous jobs', and the optional restriction to one session adds scope. It distinguishes itself from sibling tools like remote_job_status, remote_job_result, and remote_job_cancel, which target individual jobs.

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 on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The only implied usage is that it lists jobs, but there is no explicit comparison to remote_job_status or other job-related tools.

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