read_execution_output

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

No annotations are provided, so the description must carry behavioral context. It usefully discloses that output is returned as a bounded base64 page and can be read while the execution is still running, but it omits permissions, error behavior, and how the page relates to offset/length semantics.

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 short sentence with no filler, and the key qualifiers are front-loaded: bounded, base64, output page, and including while running.

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?

This is a five-parameter required-input tool with low schema description coverage, no output schema, and no annotations. The description is too thin to fully explain how to use the tool correctly or how it differs from related execution-output tools.

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 only 20%, with only the owner parameter documented in the schema. The description does not explain the five required parameters beyond a vague notion of a 'page', leaving stream, offset, length, and id semantics largely implicit.

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 gives a specific verb and resource: reading a bounded base64 output page, including while execution is running. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as read_output_log or execution_status.

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 'including while running' implies that this tool is useful for live output reads, but there is no explicit guidance on when to use it versus read_output_log, execution_status, or other execution-related siblings. No exclusions or alternatives are named.

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