oz_agent_run_cloud

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

Discloses key behavioral traits: credits consumed, returns immediately without waiting, requires CLI and account. No annotations to contradict. Could add details on error handling or limits, but covers main points well.

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?

Very concise with three front-loaded sentences covering purpose, warnings, and post-call behavior. No extraneous words.

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?

Covers invocation, post-call polling, and prerequisites. Without output schema, could specify return type more explicitly, but 'returns the run id' is sufficient.

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 has 100% description coverage, so baseline is 3. Description does not add significant meaning beyond what's already in the schema.

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?

Clearly states 'Launch a Warp Oz AI agent in Warp's cloud (not on the local machine)', specifying verb, resource, and location distinction from sibling tool oz_agent_run.

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?

Explicit warning about credit consumption with user confirmation, instructions for post-call polling via oz_run_get, and prerequisites (oz CLI, Warp account with credits). Clearly differentiates from local run.

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