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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds some behavioral value by indicating that the response includes progress, results, and paginated output, but it does not explain wait_seconds behavior or whether progress can be partial or final.

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 short, but it is under-specified rather than appropriately concise. It is not front-loaded with a clear action or resource, so its brevity creates ambiguity instead of efficiency.

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 tool with five parameters, no schema descriptions, and no output schema, the description is too sparse to be complete. It mentions progress, results, and pagination but omits essential details about required identifiers, wait behavior, pagination mechanics, and the shape of returned job output.

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?

Schema description coverage is 0%, so the description must explain the five parameters, yet it gives no meaning for workspace, job_id, wait_seconds, cursor, or output_offset. The phrase 'paginated output' vaguely gestures at pagination but does not compensate for the complete lack of parameter documentation.

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 lists output categories (progress, results, paginated output), which hints at a read operation, but it does not state a specific verb or resource such as 'retrieves a job.' It is recognizable as job-related only because of the tool name and annotation title, not because the description clearly distinguishes it from siblings like jobs_cancel.

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 such as jobs_cancel or other read tools. There are no exclusions, prerequisites, or contextual triggers to help an agent select it correctly.

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