run_maestro_flow

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

Discloses that on failure it generates a failure bundle with screenshot and logs, and returns structured results. No annotations exist, so description carries full burden; it could mention blocking behavior or side effects but is adequate.

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 concise sentences, front-loaded with main purpose and key behavioral traits, no superfluous information.

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 purpose, return value summary, and failure handling. No output schema, so description explains key outputs. Could be slightly more detailed on return structure, but sufficient for a complex tool.

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 100% with descriptions for each parameter. The description adds context about the failure bundle linking to generateFailureBundle, adding value beyond 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?

The description clearly states the tool runs a Maestro E2E test flow and returns structured results with step-by-step status, distinguishing it from sibling tools like launch_app or inspect_logs.

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?

Implies usage for E2E testing flows, but lacks explicit when-to-use or when-not-to-use guidance. No direct alternative is mentioned, but context makes it clear among siblings.

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