export_to_pptx

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

With no annotations, the description must convey behavioral traits. It indicates the tool operates on the frontmost presentation, but does not disclose error behavior (e.g., if no presentation is open), overwrite behavior for existing filePath, or any side effects. The description provides minimal but sufficient transparency for a straightforward export action.

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 of 11 words with no redundant information. It is concise and directly states the tool's purpose without unnecessary elaboration.

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 simplicity of the tool (one required parameter, no output schema, no annotations), the description is minimally complete. It covers the basic function but lacks contextual details about error handling, requirements, or comparison with similar tools. For a one-parameter export, this may be acceptable, but additional context would improve completeness.

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 coverage is 100% and the schema already describes filePath as 'Absolute POSIX path for the output .pptx file'. The description does not add any additional meaning beyond what the schema provides, so it meets the baseline expectation without exceeding it.

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 'exports', the resource 'frontmost Keynote presentation', and the output format 'Microsoft PowerPoint (.pptx) file'. It effectively distinguishes this tool from siblings like export_to_pdf or export_slide_to_image by specifying the file format.

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 implies usage when the user wants a .pptx file from the frontmost presentation, but it does not provide explicit guidance on when to use this tool vs alternatives (e.g., export_to_pdf), nor does it state prerequisites (e.g., must have an open presentation). The context is clear but lacks exclusionary or comparative notes.

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