ppt_render_slide

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that external programs (PowerPoint or LibreOffice) are required, but does not state whether the tool writes files to disk, how existing files are handled, what the return value is, or any potential side effects. This leaves the agent without critical behavioral context.

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 sentence, which is concise in length. However, it is under-specified rather than effectively concise: it omits essential details about a tool with six parameters and no schema descriptions. The brevity does not earn its place because it fails to communicate the information an agent needs.

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 the tool's complexity (six parameters, zero schema coverage, no annotations, and an output schema that is not described), the description is severely incomplete. It does not explain parameter usage, output format, environmental prerequisites, or error handling, making it nearly impossible for an agent to use the tool correctly without additional documentation.

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?

The schema has 0% description coverage, so the tool description must explain parameter semantics. The description only hints at 'single slide' (slide_number) and 'high-resolution' (possibly dpi), but provides no explanation for renderer, output_dir, output_path, or presentation_path. An agent cannot infer the meaning or usage of these parameters from the description.

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 a specific action: rendering a single slide to a high-resolution PNG. It implicitly differentiates from the sibling tool 'ppt_render_presentation' by focusing on a single slide rather than the entire presentation, though it does not name the sibling explicitly.

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 mentions two rendering engines (PowerPoint COM and LibreOffice headless) but provides no guidance on when to use each or why they matter. It does not explain when to prefer this tool over alternatives like ppt_render_presentation, nor does it state any exclusions or requirements for use.

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