Run automation script

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses very little: nothing about side effects on the target device, permissions, blocking/timeout behavior, or what happens on script failure. 'Portable', 'semantic locators', and 'cross-platform' describe the DSL flavor but not execution behavior an agent needs to invoke this safely.

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 and no repetition of the title. It is arguably too terse for a tool with a nested target object and two mutually alternative script inputs, but it wastes nothing.

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 fairly complex tool (nested target object with six target types, two alternative script inputs, no output schema, no annotations), the description omits how the script is supplied, what a run produces, and any failure/timeout semantics. An agent would need to open the schema and guess at the rest.

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% and the nested target object is fully documented in the schema, so the baseline of 3 applies. The description's 'against a target' adds no syntax or meaning beyond the schema, and it never clarifies the path-vs-yaml alternative for supplying the script.

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 pairs a specific verb (Execute) with a specific resource (a portable YAML automation DSL script) and its scope (against a target), so an agent understands this runs whole scripts rather than single actions. It does not, however, differentiate itself from near-siblings like computer_run_ui_test, computer_execute_task, or computer_action.

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?

There is no guidance on when to reach for this tool versus computer_action (single step), computer_execute_task, or computer_run_ui_test, nor any prerequisite or exclusion. The only hint is the phrase 'against a target', which merely restates the schema.

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