Import a PowerPoint file

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

Annotations declare this is a non-read-only operation and not open-world. The description adds useful behavioral context by describing what is preserved, what is skipped, and that it returns slides like get_presentation. It does not explain overwrite behavior or file-creation side effects for the target path.

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 dense and front-loaded, covering conversion behavior, preserved elements, skipped elements, and return shape without wasted words. Two sentences do substantial work.

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 non-read-only import tool with no output schema, the description sufficiently explains what is produced and what happens to slide content. It leaves some gaps around target path/overwrite semantics, but those are partly covered by the schema.

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 67%, with path and pptx documented in the schema and overwrite undocumented. The description adds no parameter-level detail beyond identifying the .pptx input, so the schema carries most of the semantic burden.

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 states a specific verb and resource: converting a .pptx into a GlideDeck project. It details exactly how slides map to frames, including preserved elements and skipped element types, making it easy to distinguish from export_pptx.

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 makes the import context clear, but it does not explicitly say when to choose this tool over alternatives such as create_presentation or open_in_editor, nor does it state when not to use it. Usage is implied rather than guided.

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