list_jobs

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

Description mentions 'recent' but does not define recency (e.g., time window or number of jobs). Returns status/progress/errors as stated, but lacks details on filtering or output format. No annotations to supplement.

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?

Single sentence efficiently conveys verb, resource, and included details. No unnecessary words.

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 no parameters and presence of output schema, the description is mostly adequate but lacks clarity on scope (e.g., all jobs or per user?) and recency bounds.

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?

No parameters are defined, so the description does not need to explain any. Schema coverage is 100% empty. Brief description is sufficient but could explicitly state no required parameters.

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 tool lists recent system jobs with specific details (status, progress, errors). It distinguishes from sibling list_ tools which focus on other resources like apps or datasets.

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?

Implied usage (view recent jobs) but no explicit guidance on when to use or when not to, nor reference to sibling tools like list_alerts which might overlap.

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