Build PPTX (creates the actual presentation file)

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It clearly states that the tool writes a file to disk, produces one image-backed slide per HTML input, preserves input order, and returns the saved file path. It could go further by noting overwrite behavior or whether the output directory must exist, but the core side effects and output behavior are disclosed.

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 compact and front-loads the essence with 'THE DELIVERABLE TOOL,' though that opening phrase is somewhat redundant given the title already says 'creates the actual presentation file.' The rest is efficient: it explains the mechanism, the ordering, the distinction from preview_slide, and the result to report.

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 file-generating tool with no output schema, the description covers the key contextual needs: what input is required, how it is processed, that a file is saved to disk, and that the serialized output is the file path. The schema handles parameter details, and the sibling is addressed explicitly. It could mention edge cases or constraints around HTML rendering, but the definition is largely complete for correct invocation.

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 100%, so the schema already documents width, height, slides, and outputPath adequately. The description adds some nuance by emphasizing that each HTML document becomes 'one image-backed slide' in the given order, but it does little to clarify parameter formats beyond what the schema provides. This is the baseline 3 expected when the schema is the primary source of parameter meaning.

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 names a specific verb and resource: 'Renders a list of complete HTML documents... and assembles them into a single PowerPoint (.pptx) file written to disk.' It also distinguishes itself from its sibling by saying 'Call this — not preview_slide — whenever the user asks for a PPT/PowerPoint/presentation/apresentação/slide deck.' This leaves no ambiguity about what the tool produces or how it differs from preview_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 explicitly states when to use this tool versus the alternative: 'Call this — not preview_slide — whenever the user asks for a PPT/PowerPoint/presentation/apresentação/slide deck.' It also explains what to do with the result: 'the tool result gives you the saved file path to report back to the user.' This gives the agent both a trigger and a follow-up action.

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