export_png

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write profile is covered. The description usefully adds that 'view changes the camera first' (a state side effect) and that dimensions are in pixels, but it never explains the destructive hint — file overwrite behavior, failure modes, or permissions are unstated.

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 short, dense sentences, front-loaded with the core action and example, then the two most easily misused parameters. Nothing is wasted.

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?

Wait—reconsidering: for a 5-parameter destructive write tool with no output schema and 0% schema coverage, the description omits the overwrite semantics implied by destructiveHint=true and the 'transparent' parameter entirely.

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 5 parameters, so the description must compensate. It clarifies 'path' via example and gives units for width/height plus the camera side effect of 'view', but says nothing about 'transparent' or how PNG vs JPG is selected (presumably the extension).

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: 'Export the viewport as a PNG/JPG file', with a concrete path example. It does not, however, distinguish itself from close siblings such as 'screenshot' or 'export_file', so an agent cannot tell them apart from this text alone.

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 when-to-use guidance and no mention of the obvious alternatives ('screenshot', 'export_file') that appear in the sibling list. The reader must guess which export tool to pick.

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