执行受限 ENVI GUI 配方

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

Annotations are all false, so the description carries the burden. It discloses the dry_run behavior (no GUI operation) and the sequential nature plus the 100-action limit. However, it does not explain potential side effects of non-dry-run execution, failure handling, or what 'restricted' means in practice.

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 one compact, front-loaded sentence covering core functionality and dry_run. No wasted words, every phrase adds value.

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?

This is a complex tool with an actions array of many fields, but the description omits crucial context: how to specify session_id, how actions are structured, error handling, and the meaning of 'evidence screenshots'. The output schema exists but does not replace the need for usage context.

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 0%, so description must compensate. It explains the actions parameter by listing supported action types and describes dry_run explicitly. However, it does not mention session_id or how to structure the actions array, leaving significant gaps for 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 specifies the tool's function: sequentially executing up to 100 restricted GUI actions (menu, wait, click, type, key, sleep, capture). It also mentions dry_run validation, which distinguishes it from sibling tools that perform individual actions. This is a specific verb+resource statement.

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 gives clear context: it is for executing a batch of actions in sequence, and dry_run mode is for validation only. It does not explicitly mention alternatives or exclusions, but the context strongly implies batch use versus calling sibling tools individually.

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