ppt_render_presentation

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It states the action (render to PNG) but does not disclose whether the operation modifies the presentation, requires the file to be open, or what files it creates (e.g., output directory handling). The output schema may cover the return format, but side effects and constraints are unspecified.

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 a single, front-loaded sentence with no fluff. Every word contributes to the core purpose, making it easy to parse quickly.

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 tool with four parameters, no annotation coverage, and no schema descriptions, the description is too minimal. It lacks information on parameter usage, side effects, file handling, and any constraints (e.g., whether the presentation must be opened first). The output schema exists but the description does not bridge the gap for a correct call.

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 for the four parameters (dpi, renderer, output_dir, presentation_path). It provides no explanations of these parameters, their defaults, or how they affect rendering. An agent cannot know what 'renderer' options exist or how 'output_dir' is used.

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 verb 'render' and the resource 'all slides in the presentation', and specifies the output format 'PNG images'. It is distinct from sibling ppt_render_slide, which is implied by the 'all slides' scope, so an agent can differentiate.

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 does not explicitly mention when to use this tool vs alternatives like ppt_render_slide, nor does it state any exclusions or prerequisites. The 'all slides' phrasing gives some implication for batch rendering, but there is no direct routing guidance.

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