export_slide_to_image

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

No annotations are provided, so the description carries full burden. It discloses a key behavioral trait: 'Exports all slides to a temporary directory, then copies the specific slide image to the target path.' This reveals temporary side effects and inefficiency, which is valuable for an agent. However, it does not mention cleanup of the temp directory or potential errors.

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?

Two sentences, no redundancy. The first sentence states the core purpose, the second adds valuable behavioral context. Every word earns its place; the description is efficient and well-structured.

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 no annotations and no output schema, the description provides sufficient context for a simple export tool. It explains the mechanism and implies file creation. However, it lacks details on cleanup behavior, error conditions, or return value (e.g., success indication). Still, for a single-purpose tool, it covers the essential points.

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 all three parameters (format, filePath, slideIndex). The description adds minimal extra meaning beyond confirming the copy action for filePath. Baseline 3 is appropriate as it does not significantly enhance parameter understanding.

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 action: 'Exports a single slide as an image file.' It specifies the resource (single slide), verb (exports), and output format (image file). The mechanism (export all slides then copy) further clarifies the tool's operation, distinguishing it from sibling export_to_images.

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 implicitly suggests use for single slide export, contrasting with export_to_images which likely exports all slides. However, there is no explicit guidance on when to use this tool versus alternatives, or mention of prerequisites like open presentation. The usage context is implied but not fully articulated.

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