ppt_create

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

No annotations are provided, and the description fails to disclose key behaviors such as whether existing files are overwritten, what permissions are required, or what the function returns. It only specifies the input format, leaving side effects and error handling unclear.

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 concise sentence that front-loads the purpose and includes the essential input format. There is no wasted wording, and it reads clearly.

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 absence of annotations and output schema, the description is the sole source of information. It covers the key input (path and slides) but leaves out return behavior, overwrite semantics, and error handling, making it minimally viable but not fully complete for an agent to use without uncertainty.

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?

The input schema is empty, so the description is entirely responsible for parameter semantics. It introduces `path` and the slides array with a clear shape ({title, bullets:[…]}), which is meaningful and helpful. However, it omits explicit types and any optional parameters, so it does not fully compensate for the absence of 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 the action (creates), the resource (PowerPoint .pptx), and the destination (path), and specifies the input structure as an array of slides with title and bullets. This distinguishes it from sibling tools like ppt_read and other document creation tools.

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 for creating presentations, but it does not explicitly state when to use this tool over alternatives such as ppt_read or word_create. There are no mentions of prerequisites, exclusions, or preferred contexts, so the agent must rely on the verb 'creates' to infer usage.

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