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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context that saved artifacts may not include live worker logs and that reads are bounded previews, but it omits details such as truncation behavior, error conditions for bad filenames, or permission requirements.

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 tightly written sentences with the primary capability front-loaded and the important live-logs caveat immediately following. There is no redundant or filler text.

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 read-only job-log tool with no output schema, the description adequately covers the two modes and notes the saved-artifact limitation. It remains incomplete regarding output shape beyond listing/preview, bounding behavior, and why max_bytes and max_lines are required despite having defaults.

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 carry parameter meaning. It clarifies that filename must be exact and that previews are bounded, which loosely maps to max_bytes and max_lines, but it does not explain those limit parameters, their interaction, defaults, or the required job_id.

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 uses specific verbs and resources: listing saved log artifacts for a job or reading a bounded preview by exact filename. It clearly distinguishes log artifacts from live worker logs, though it does not explicitly name or contrast with sibling tools such as read_job_file or get_job.

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 imply usage: omit filename to list artifacts, provide an exact filename to read a preview. However, it gives no explicit guidance on when to choose this tool over alternatives like get_job, get_result, or read_job_file, and no exclusions or prerequisites are stated.

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