run_airtest_code

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

With no annotations to rely on, the description must disclose behavioral traits. It does mention that the code runs in a 'temporary .air project,' which hints at environment isolation. However, it does not warn about potential side effects on the device, mention that arbitrary Python code can be executed, or explain error/timeout behavior. The 'trusted' qualifier is a minimal safety nod but far from sufficient.

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?

The description is a single, front-loaded sentence that effectively communicates the core action. There is no redundancy or filler, earning a high score for conciseness.

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?

Given the tool's complexity (executing arbitrary Python code), the lack of annotations, and the minimal description, the tool is under-specified. While the output schema exists and may describe return values, the description does not address safety, device interactions, or how this integrates with the sibling toolset. The 'temporary .air project' detail is a small positive, but overall the description is incomplete for such a powerful 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?

The input schema lists three parameters (code, device, timeout) with 0% schema description coverage. The description does not mention any of these parameters, nor does it explain that 'code' is required, how 'device' should be formatted, or what the timeout controls. The description adds no value to parameter understanding.

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 identifies the tool as executing 'trusted, hand-written Airtest Python code' within a 'temporary .air project.' This specific verb-resource pair distinguishes it from sibling tools like run_airtest_script (which presumably runs existing scripts) and the point-action tools (touch/swipe).

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 word 'trusted' implies a safety condition for use, but there is no explicit guidance on when to choose this over run_airtest_script or the individual action tools. The description does not discuss prerequisites or typical scenarios, making the usage guidance implied rather than explicit.

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