export_png

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

Annotations already declare openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds destination-selection context ('project or configured directory'), but says nothing about the overwrite flag's effect on existing files or the scale/background rendering behavior, which matter for a file-writing tool.

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 well-formed sentence with the action and output format front-loaded and no filler. Its brevity is appropriate, though the space saved was not used to convey any parameter or usage detail.

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?

An output schema exists so return values need not be explained, but for a six-parameter mutation-style file writer with zero schema description coverage, the description leaves too much unstated: defaults, overwrite semantics, and how the destination is resolved.

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% across six parameters, and the description only obliquely touches the 'directory' parameter. Nothing explains what 'scale', 'padding', 'background', or the required 'name' pattern mean in practice, so the agent gets no semantic help where the schema provides none.

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 (Export) and resource (the active scene) plus the output format (PNG image file), which distinguishes it from the sibling export_scene. It does not explicitly contrast with preview or save, but the format specificity is enough for an agent to identify 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?

There is no guidance on when to choose this over export_scene, save, or preview, and no stated prerequisites. The destination phrase 'in a project or configured directory' hints at context but does not tell the agent how to decide.

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