render_frame

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a single-frame visual preview, but it does not disclose that a file is written to the given output path, nor whether the app must be connected first. There is mild tension between writing a .png and readOnlyHint, but 'read-only' here reasonably means the project is not modified, so this is not a contradiction.

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?

A single front-loaded sentence with the action and result first and the rationale trailing. No filler or redundancy.

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?

There is no output schema, and the description never says what the call returns (a path, a confirmation, image data) or whether connect_app is required when project is omitted. For a four-parameter render tool, these gaps leave the agent guessing about the response and prerequisites.

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 100%, so all four parameters are documented in the schema itself. The description adds only the qualifier 'Program', which usefully implies the time parameter indexes the program timeline rather than a source clip, but nothing further about scale, project, or output formats.

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?

States a specific verb and resource: 'Render one Program frame to an image.' The word 'one' and 'Program frame' implicitly distinguish it from siblings like export_frames and render, but it never names those siblings explicitly, so the agent must infer the boundary.

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?

'to look at the edit' implies a preview/inspection use case rather than a deliverable export, which is useful but only implied. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., export_frames vs render vs export_timeline) to guide selection.

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