save_template

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that a region of the current frame is saved and clarifies the coordinate space, but omits critical details such as whether existing templates are overwritten, what permissions are needed, and what the tool returns or errors on.

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, well-structured sentence with no wasted words. The core action and coordinate context are front-loaded.

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 five required parameters, no annotations, no output schema, and zero schema description coverage, the description is too thin. It does not explain what the tool returns, how errors are handled, or any behavioral expectations, leaving significant gaps for an agent to call it correctly.

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 0%, so the description must compensate. It clarifies that x, y, width, and height use full 1920x1080 coordinates, and implies name is the template identifier, but it does not define coordinate origin, whether width/height are inclusive, or any constraints on name.

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 uses a specific verb ('Save') and resource ('region of the current frame ... as a template for wait_for'), making the tool's function immediately clear. It does not explicitly differentiate itself from siblings like list_templates, so it stops short of a 5.

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 phrase 'as a template for wait_for' implies the tool is used when preparing a template for later matching, but there is no explicit guidance on when to use it versus alternatives or any prerequisites. Usage is only implied, not stated.

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