app.export_all_png

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

With no annotations, the description must carry behavioral weight. It usefully discloses the output filename pattern and that a list of paths is returned, but omits whether existing files are overwritten, whether out_dir must already exist, and how failures are reported — real concerns for a tool that writes to disk.

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 sentences with no filler; the naming convention and the directory scope are front-loaded, and the return value follows. Every sentence earns its place.

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?

For a one-parameter export tool with no annotations and no output schema, the description covers the essentials (naming, destination, return type) but leaves gaps around overwrite behavior, directory prerequisites, and output format/size that an agent might need before invoking it.

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?

The single parameter out_dir has 0% schema description coverage, so the description must compensate. It does add meaning by stating that files are written into that directory with the slide_NN.png naming scheme, but leaves open whether the directory must exist or is created.

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 every slide as slide_NN.png in the given directory' — which is clearly distinguishable from the single-target app.export_png sibling in scope ('every slide'). It does not explicitly name or contrast with that sibling, so it falls just short of 5.

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 word 'every slide' implies bulk export versus the sibling app.export_png for a single slide, but the description never names the alternative or states when to prefer each. Usage must be inferred from the scope wording rather than read directly.

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