ppt_create

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states that it creates a file with title and bullet slides, lacking details on file creation location, overwrite behavior, permissions, side effects, or return value. Many behavioral traits are left unknown.

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, front-loaded sentence without any redundant information. Every word earns its place, making it highly efficient.

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 simple functionality (creating a file with title and bullet slides) and lack of parameters or output schema, the description is minimally adequate. However, it omits important details such as where the file is saved, naming conventions, and what the tool returns, which would help the agent fully understand the outcome.

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 tool has zero parameters and the schema coverage is 100% (empty). According to the rules, 0 parameters yield a baseline of 4. The description adds meaning by explaining what the tool produces, which compensates for the lack of parameter documentation.

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 'Creates', the resource 'PowerPoint (.pptx) file', and the content 'with title and bullet slides'. It effectively distinguishes from sibling tools like ppt_read (read) and other creation tools (word_create, excel_create).

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 a simple bulleted PowerPoint, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., when title and bullet slides are sufficient vs. more complex layouts). No exclusions or prerequisites are mentioned.

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