Read a bounded tail from a longrun job

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

Annotations already provide readOnlyHint=true, so the description's 'Read only' adds no new safety info. It does add that the tail is 'stored' and 'bounded', which hints at behavior (not live streaming, limited size), but lacks details on error handling or response structure.

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 a single, efficient sentence with no redundancy. It front-loads the core action and resource without waste.

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 tool is relatively simple with an output schema (so return values are covered), but the description lacks parameter semantics and usage guidance. It is not fully complete for a 3-parameter tool with zero schema description coverage.

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 0%, so the description must compensate by explaining parameters. It only mentions 'known job ID' and 'bounded tail', but does not explain tail_bytes or tail_lines, their defaults, or how they interact. The agent must rely on schema names/types alone, which is insufficient.

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 a specific action ('Read only') and resource ('bounded tail stored for a known job ID'), distinguishing it from siblings like health (status) and run_and_wait (execution). The title reinforces the longrun job context.

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 phrase 'known job ID' implies this tool is used after a job has been created (likely via run_and_wait), but no explicit when/when-not guidance or alternatives are mentioned. Usage context is implied rather than stated.

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