render_current_frame

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

No annotations are provided, so the description carries full behavioral burden. It discloses that the tool exports an image and requires specific conditions, but does not mention potential delays, error handling (e.g., if no frame), output format details, or side effects. Adequate but could be more transparent.

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?

Three concise sentences with no wasted words. The main action ('Export the frame...') is front-loaded, and the rest provides context. Every sentence serves a purpose.

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 no output schema, the description covers the essentials: what it does, when to use, and prerequisites. It lacks explicit mention of return format or error states, but for a simple tool with no parameters, it is largely 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?

The input schema has no parameters and schema description coverage is 100% (trivially). Per the rule, baseline is 3. The description adds no parameter information because there are no parameters, so score 3.

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 the tool exports the current frame as an image, using a specific verb ('Export') and resource ('frame at the playhead'). It also distinguishes itself from the sibling 'get_state' by emphasizing visual evidence over metadata.

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?

Explicitly states when to use ('to look at what the timeline actually shows before and after an edit, rather than reasoning from metadata alone') and provides a prerequisite ('timeline must be open and a frame visible'). This effectively guides the agent on when to invoke this tool vs. alternatives.

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