render_frame

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While it accurately states that a frame is rendered and saved to disk returning a file path, it omits important behavioral traits such as potential overwriting of files, performance impact (e.g., rendering time), whether the operation is read-only, or permission requirements. These gaps leave the agent without critical context for safe invocation.

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 two sentences (22 words), front-loading the primary action and result. Every sentence contributes value, and there is no extraneous information.

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?

With no output schema, the description adequately notes the return value (file path). However, given the tool has five optional parameters, the description does not clarify how to identify the composition (compId vs compName) or handle defaults. It is minimally complete for a simple render but could better guide the agent on parameter usage.

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 100%, so the input schema already documents all parameters with descriptions. The description adds no additional meaning to the parameters beyond what the schema provides. Baseline 3 is appropriate, as the description does not improve parameter understanding beyond the schema.

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 action ('Render a single frame'), the resource ('a composition'), the output format ('PNG file on disk'), and the return value ('file path'). It distinguishes this tool from siblings, as no other tool in the list renders frames to disk for visual inspection.

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 implies use when the AI needs to 'inspect what the comp actually looks like,' which is a visual context. However, it does not explicitly state when to use this tool versus alternatives (e.g., get_comp_report for text reports), and it provides no exclusion criteria or prerequisites.

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