list_jobs

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

With no annotations, the description carries the full burden, but it only states the basic purpose and lists parameters. It does not disclose side effects, permissions, data scope (e.g., all jobs or user's jobs), pagination behavior, or any limitations. This is insufficient for a listing operation.

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 extremely concise: one sentence for the overall purpose followed by a compact bullet list of parameters. Every sentence adds value, and the most important information (action and resource) is front-loaded.

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 covers purpose and parameters but lacks broader context. No output schema is provided, and the description does not explain the return format, the default ordering, or how pagination works. It also doesn't help differentiate from similar list tools like list_runs.

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 0% description coverage, and the description fully compensates by providing a concise explanation for all 6 parameters. Each parameter gets a clear one-line description (e.g., 'skip: Number of records to skip'), adding significant meaning beyond the schema's types and defaults.

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 explicitly states 'List batch jobs with optional filtering and sorting', clearly indicating the verb (list) and resource (batch jobs). The presence of many sibling list tools (e.g., list_runs, list_pipelines) makes the purpose distinct enough.

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, no exclusions, and no context about when not to use it. The description simply states what it does without any comparative or conditional advice.

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