Render slides

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior. The description adds value beyond them: a hard cap of 8 returned images and the fact that save=true writes PNG files named <name>_s<N>.png, so the agent knows a disk side effect exists despite readOnlyHint.

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 dense sentence with no filler, and the core capability plus the two most decision-relevant facts (8-image cap, PNG-on-save) are front-loaded. Slightly awkward grammar costs it the top mark.

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 an 8-parameter tool with no output schema, one sentence is thin. It never says what is returned when save=false (presumably inline images), what happens when the selection exceeds the 8-image cap, or how slides interacts with the ordering of outputs.

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 63%, mid-range. The description explains only one parameter's effect (save=true yields PNGs with a naming pattern); scale, slides, overwrite, output_dir, output_path and save_scale are left entirely to the schema. Adds marginal meaning without compensating for the uncovered parameters.

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 concrete verb-and-resource outcome: producing pictures of slides from a PowerPoint or DeckCraft file, with the output count and file naming. It distinguishes itself from read-oriented siblings like get_presentation_info or open_in_deckcraft, though the phrasing 'Pictures of slides ... to look at them' is roundabout rather than a clean verb+object.

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 when-to-use guidance, no prerequisites, and no alternatives named among the many siblings (convert_presentation, get_presentation_info, open_in_deckcraft). The only implicit cue is that this is the way to visually inspect slides.

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