Render PNG frame

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and non-idempotent, so the agent knows this is a write-like operation. The description adds that it writes a file to the local machine, which is useful context, but says nothing about overwrite behavior, blocking/duration, or rate limits for large renders.

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?

Two tight sentences with the core action and output location front-loaded, then the practical path constraint. Every clause earns its place with no filler.

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?

Adequate for a single-output render tool: the action, destination, and path format are covered. With no output schema, it could say what is returned (e.g., path or success) or whether an existing file is overwritten, but the description is otherwise sufficient to call 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 100% and already documents all three parameters, including the path and extension behavior. The description largely restates 'absolute path' and the auto-appended .png extension rather than adding syntax or format meaning beyond the schema, so the baseline 3 is appropriate.

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 (Render) and resource (the active composition to a PNG file), plus the scope (active composition, local machine). No sibling tool performs rendering, so it is unambiguously distinguishable from the layer/attribute/keyframe manipulation tools around it.

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 parenthetical '(useful for checking your work visually)' implies a usage context, but there is no explicit when-to-use/when-not, no prerequisites, and no named alternative. Usage is only implied, which matches the 3 baseline.

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