render_slides_as_pngs

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

With no annotations, the description must itself convey behavioral traits. It discloses the output type (PNG sequence) and a dependency (compiled artifact), which is useful. However, it does not explicitly state whether the operation is read-only or if any side effects occur, leaving some ambiguity that annotations would normally cover.

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?

The description is extremely concise—two short sentences—with the core purpose front-loaded. Every word earns its place, and there is no redundancy or filler.

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?

The description covers the essential purpose and a key prerequisite, and an output schema exists to document return values. However, it could be more complete by explicitly mentioning that the presentation must be compiled first or by clarifying the optional parameters (dpi, output_dir). The current text is adequate but leaves room for an agent to misunderstand the workflow.

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%, so the description must compensate. It only adds meaning for the 'format' parameter (must match a previously compiled artifact), but does not explain presentation_id, dpi, or output_dir. The schema's defaults and types provide some information, but the description adds little beyond the format constraint.

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 converts a compiled artifact into a numbered PNG sequence for visual validation. It uses a specific verb ('Convert') and resource ('compiled artifact'), and the mention of 'numbered PNG sequence' distinguishes it from sibling tools like compile_presentation or get_slide.

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 gives a clear use case ('for visual validation') and a prerequisite ('format must match a previously compiled artifact'), implying this tool is used after compilation. It does not explicitly name alternatives or state when not to use it, but the context suffices for a well-informed agent.

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