ppt_create

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

No annotations are provided, so the description carries full behavioral disclosure burden. It only states it creates a file but omits key traits such as whether existing files are overwritten, required permissions, file size limits, or error handling. For a mutation tool, this is insufficient.

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, well-structured sentence that front-loads the core purpose. Every word earns its place with no redundancy or fluff.

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 file-creation tool with 2 parameters and no output schema, the description covers the basic input structure. However, it lacks details on overwrite behavior, return values, or potential errors, leaving gaps for an agent that needs to invoke it correctly.

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 100% and the description adds 'each with a title and optional bullet points', which echoes the schema but does not add new meaning beyond what the property descriptions already provide. Baseline 3 is appropriate; no extra constraints or format details are given.

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 tool creates a .pptx file from a list of slides, each with a title and optional bullet points. The verb 'create' and resource 'PowerPoint file' are specific, and it distinguishes itself from siblings like word_create (Word files) and note_set (notes).

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 PowerPoint files but offers no explicit guidance on when to choose it over alternatives like word_create or note_set. Sibling tools exist, so additional context about when to use each would be beneficial but is missing.

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