create_presentation

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

No annotations are provided, so the description carries full behavioral burden. It discloses that a new .pptx file is created, but does not mention what happens if the file already exists, whether directories are created, what is returned, or any side effects beyond file creation.

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 compact and front-loaded: a clear one-line purpose followed by a short parameter list. It contains no filler, and each element adds useful semantic information.

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 simple two-parameter creation tool, the essential call is adequately specified. However, with no annotations and no output schema, the description leaves out important contextual details such as overwrite behavior and expected return value, making it adequate but not complete.

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 0%, so the description must add meaning. It does: 'path' is clarified as an absolute file path, and 'title' is explained as an optional title for the first slide, which goes beyond the bare schema properties.

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 verb and resource: 'Create a new PowerPoint presentation (.pptx).' This distinguishes it from sibling tools like add_presentation_slide, add_presentation_text, and read_presentation at a basic level, though it does not explicitly call out those alternatives.

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 phrase 'Create a new PowerPoint presentation' implies this is the entry point before adding slides or text, and the sibling set shows Excel/Word alternatives. However, there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance; the agent must infer the workflow.

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