get_execution_output

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

With no annotations, the description carries the behavioral burden. It discloses that the operation returns a single bounded chunk rather than full output, and that phase filtering is available. It does not discuss pagination semantics or encoding, but for a read-only retrieval tool this is meaningful behavioral context.

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?

A single front-loaded sentence with no filler; it states the action, resource, chunking behavior, and phase option compactly.

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 simple read-oriented tool with a rich output schema and a single required parameter, the description plus schema is mostly sufficient to invoke correctly. It could better explain paging/offset semantics, but with defaults and constraints in the schema this is a minor gap.

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 compensate. It clarifies phase_name ('one named phase') and the bounded-chunk nature of max_bytes/offset, but it does not define offset semantics or explicitly connect execution_id to the required parameter. The schema's self-explanatory titles and constraints carry much of the remaining weight.

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?

States a specific action ('Retrieve') on a specific resource ('execution output') and narrows it to a bounded chunk with optional phase scoping. It is clear enough for selection, though it does not explicitly distinguish itself from sibling tools like get_execution or get_capture_slice.

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 'for all phases or one named phase' gives context about when phase_name matters, but there is no explicit guidance on when to prefer this tool over alternatives or when not to use it. Usage 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.