preview_slide

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

No annotations exist, so the description must disclose behavioral traits. It mentions it 'reads the rendered slide configuration' and 'produces a preview', implying a non-destructive read operation, and explicitly says 'without compiling' which suggests no heavy side effects. However, it doesn't clarify whether it requires prior compilation, network access, or any side effects like caching. It doesn't state if it's read-only or if it writes temporary files. So it's partially transparent but not comprehensive.

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?

Description is concise, clear, and front-loaded. It conveys key purpose and input semantics in two sentences, no fluff.

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?

Given no annotations and 0% schema coverage, the description provides essential info but lacks detail on boundary cases, exact parameter formats, and potential side effects. Output schema exists but not detailed here. It's adequate but not exhaustive.

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 has zero description coverage for 6 parameters. The description explains scene, slide_index, and output_format (implies image/video/gif formats), but workspace_dir is not explained. It adds meaning beyond schema by explaining that scene is a rendered scene, and slide_index is the slide to extract. It adds enough to use the tool, but incomplete for all params.

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?

The description clearly states the tool's function: 'Extract a single-slide preview' from a slide deck without compiling. This specific verb+resource phrasing distinguishes it from siblings like compile_presentation and serve_revealjs_html, which handle the full compilation/serving lifecycle.

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 description says 'without compiling the deck' which gives a clear context for when to use this tool (quick preview). However, it doesn't explicitly state when NOT to use it or mention alternatives like list_scenes or compile_presentation. It's adequate but not explicit about exclusions.

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