cw_jobs

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

With no annotations, the description carries the burden. It usefully discloses ordering (newest first) and that payloads are omitted, but it does not state whether the operation is read-only, what "recent" means, or whether there is any pagination or retention 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 with no wasted words. Ordering and payload omission are stated efficiently.

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?

For a simple list tool with no output schema and no annotations, the description covers the high-level purpose but omits how many jobs are returned, what fields are included when payloads are stripped, and how the record set is bounded. It is adequate but incomplete.

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?

There is one optional limit parameter, and schema description coverage is 0%. The description entirely omits the limit parameter, so it fails to compensate for the missing schema documentation even though the schema does provide min/max/default values.

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 gives a specific verb and resource ("List recent background jobs") plus ordering and a payload exclusion, so an agent can tell what it returns. It does not explicitly distinguish itself from siblings like cw_job or cw_job_help, but it does characterize the list view rather than detail, abandon, or 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?

Listing "recent" jobs implies a discovery or overview use case, but the description gives no explicit when-to-use or when-not-to-use guidance. It does not route the agent to cw_job for a single job or to cw_job_help for job semantics, leaving that inference to the caller.

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