maestro_run_yaml

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

No annotations are provided, so the description carries full burden. It states 'Returns all captured screenshots as images' but omits behavioral details like side effects on device state, permission requirements, error handling, or destructive potential. For a tool that runs flows, such transparency is lacking.

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: first states purpose, second adds audience and output. No fluff, every word earns its place. Front-loaded with action and resource.

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?

The tool has 2 parameters and no output schema. Description covers primary function and output (screenshots), but lacks information about error handling, success conditions, whether it waits for flow completion, or prerequisites like Maestro setup (sibling setup_maestro exists). Adequate but not complete.

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 the baseline is 3. The description does not add meaning beyond the schema: 'Complete Maestro flow YAML content' and 'Output directory for flow results and screenshots' essentially repeat the schema descriptions. No additional context about parameter constraints or format.

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 it 'Run a Maestro flow from raw YAML content', specifying the action (run) and resource (Maestro flow from YAML). The phrase 'For advanced users' distinguishes it from simpler alternatives like maestro_run_flow, which likely runs pre-saved flows.

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 description says 'For advanced users who want full control', implying it's for a specific audience but does not explicitly name alternatives or provide when-to-use vs when-not-to-use guidance. No mention of prerequisites or context.

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