oz_run_list

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

Declares 'Read-only' and describes return fields (id, status, timing) and ordering. Since no annotations exist, the description adequately covers behavioral traits for a non-destructive list tool.

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 sentences with no wasted words. Front-loaded with purpose and key info, then usage guidance.

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?

Explains output (id, status, timing) and ordering, plus usage context linking to sibling tool. Lacks mention of default cap or pagination, but is sufficient for a simple list tool with two optional parameters.

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 100%, so baseline applies. The description adds no additional meaning beyond what the schema provides for 'limit' and 'status', but the schema itself is clear.

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 states a specific verb ('list'), resource ('Warp Oz runs'), and output fields ('id, status, timing') with ordering ('newest first'). It distinguishes from siblings by noting it is for discovering run ids to pass to `oz_run_get` or reviewing activity.

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?

Explicitly states usage: 'Use to discover run ids... or to review recent agent activity.' Provides context for when to use, though does not explicitly mention when not to use or list alternatives.

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