get_job_output

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

No annotations are provided, so the description must carry full behavioral burden. It only states that output is returned and offset enables streaming, but lacks details on output persistence, error handling, or limits. For a read tool, this is insufficient.

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 with two sentences plus an example code block. It front-loads the purpose and provides a clear example. Every element adds value without redundancy.

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?

While the description covers the basic operation and parameter usage, it lacks information about the return format (no output schema). It does not specify whether output is text, JSON, or other, leaving a gap for a tool that retrieves command 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 coverage is 100%, so baseline is 3. The description adds value by explaining the offset parameter's role in streaming beyond the schema's description, and provides an example usage, improving agent understanding.

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 'Get output from a background job with streaming support', specifying the verb and resource. It distinguishes from siblings like get_job_status and execute_command by emphasizing output retrieval and streaming.

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 gives guidance on using offset for streaming ('Use offset to get only new output since last call'). However, it does not provide explicit when-to-use or when-not-to-use relative to alternatives, such as when to call get_job_output vs get_job_status.

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