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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context not in the annotations: that live worker logs are not necessarily persisted as saved artifacts, warning the agent that absence of a saved log is not proof the job logged nothing.

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?

Two short sentences, front-loaded with the primary list behavior and the filename variant, plus the caveat. No filler; every clause earns its place.

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 two behavioral modes and the persistence caveat are covered, and the annotations carry the safety profile. But with 0% schema description coverage, no output schema, and four parameters whose units and semantics (byte/line bounds) are unexplained, the definition is only adequate for correct invocation.

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% for all four parameters, and the description only hints at 'filename' ('by exact filename') and loosely at bounds ('bounded preview'). It does not explain job_id, max_bytes, or max_lines, nor why max_bytes/max_lines are required despite having defaults, so it fails to compensate for the schema gap.

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 names a specific resource (saved log artifacts for a job) and clearly distinguishes two modes: listing artifacts vs. reading a bounded preview by exact filename. It is much more informative than the bare name, though it never explicitly contrasts itself with the nearby read_job_file or get_job siblings.

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 two modes are implied by the presence or absence of a filename, which gives the agent an implicit rule for choosing between them. However, there is no explicit when-to-use guidance relative to siblings like read_job_file or get_result, and no stated prerequisites.

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