GenOffice pptx create

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

No annotations are provided, so the description carries the burden. It discloses that it creates a NEW file with one blank slide and writes to outPath, which is reasonably transparent. However, it doesn't mention whether an existing file at outPath gets overwritten/destroyed, or any error conditions (e.g., if outPath directory doesn't exist).

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?

Three sentences, front-loaded with the core action, and zero wasted words. Every sentence conveys distinct, useful information about purpose, deferred behavior, and file destination.

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 1-parameter creation tool with no output schema, the description is mostly adequate. However, it lacks disclosure about overwrite behavior and what the return value is. Given no annotations, a bit more behavioral coverage (e.g., 'will overwrite existing file') would help.

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% (single outPath param fully documented). The description restates that outPath is where the file is written, which adds marginal value echoing the schema. Baseline 3 is appropriate since schema does the heavy lifting.

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 specific verb+resource (create a .pptx from scratch using createBlankPptx) and scope (one blank slide, written to outPath). It distinguishes from sibling genoffice_pptx_patch by explicitly saying to use that afterwards.

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?

Explicitly explains what this tool does NOT do (doesn't fill in content) and directs the agent to use genoffice_pptx_patch afterwards. This is clear when-to-use and when-not-to-use guidance with an explicit named alternative.

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