app.export_png

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

With no annotations, the description carries the full burden, and it does disclose useful implementation behavior (headless render via QGraphicsScene on a fresh QImage, no GUI widget shown). It omits mutation-relevant behavior: whether an existing file at `path` is overwritten, whether directories are created, and what is returned on success or failure.

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 tightly written sentences with the primary action front-loaded and no padding. The second sentence is arguably implementation trivia, but it is short and informative rather than wasteful.

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 write-side export tool with no annotations, no output schema, and 0% parameter documentation, the description should state return value (e.g., written file path), overwrite behavior, and index semantics. Those gaps leave the agent unsure how to invoke it safely even though the core action is clear.

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 coverage is 0% with two parameters, so the description must compensate and it largely does not: `path` format expectations and `slide_index` indexing base or default slide are unexplained. Worse, it advertises a 'default 2x = 1920x1080' scaling notion but no scale parameter exists in the schema, which can mislead the agent about available controls.

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?

Specific verb and resource: 'Render a single slide to a PNG file' with resolution scope stated. It implicitly contrasts with export_all_png via the word 'single', but never names that sibling explicitly, so differentiation is inferential rather than stated.

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?

No explicit when-to-use guidance or named alternatives, though 'single slide' hints at the boundary versus app.export_all_png and the PNG format hints at export_json. The agent must infer the selection criteria on its own.

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