create_pptx

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

No annotations are provided, so the description carries the burden of behavior disclosure. It does state the core behavior of creating a PPTX file, but it does not mention side effects such as whether an existing file at outputPath is overwritten, what the tool returns, or any file-system interactions. The behavior is mostly inferable from the 'Create' verb and the outputPath parameter, but additional transparency would help.

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 with front-loaded action and resource. It contains no unnecessary jargon or filler. The phrase 'with slides' is slightly redundant for a PPTX but still clarifies the expected content, so it does not meaningfully hurt conciseness.

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?

The schema provides strong coverage of the parameters, including the nested slide structure and output path, so the description does not need to restate those details. However, with no output schema and no annotations, the description lacks information about return values, overwrite behavior, and when to choose this tool over edit_pptx or other create tools. It is minimally adequate but leaves gaps around usage and side effects.

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%, and every parameter already has a description in the input schema, so the burden on the tool description is low. The description itself adds no new semantic detail beyond the word 'slides', which corresponds directly to the slides parameter. This meets the baseline but does not go beyond what the schema already provides.

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 names the operation ('Create') and the specific resource ('PowerPoint presentation (PPTX)'), distinguishing it from sibling file-creation tools like create_docx and create_xlsx. Including 'with slides' also disambiguates the expected artifact. This is a specific and unambiguous purpose statement.

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 the tool should be used for creating new PPTX files, and the sibling list includes edit_pptx, which implies a logical counterpart. However, there is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives like create_docx or create_xlsx. The usage context is inferred from the name and file type rather than stated.

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