edit_pptx

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

No annotations are present, so the description carries the full burden for behavioral disclosure. It omits the important default behavior that outputPath overwrites the input file, and it claims "modify content" even though the schema only supports adding slides, not editing existing content.

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 short and front-loaded, but the phrase "modify content" is redundant with "add slides" and misleading given the schema. It is concise, yet not every element earns its place.

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 tool with a nested addSlides schema and no annotations, the description should clarify that outputPath defaults to overwriting the input file and that only adding slides is supported. It currently provides only high-level intent and a misleading "modify content" phrase.

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 100%, so the schema already documents all parameters. The description adds no meaningful parameter-level details beyond loosely naming "add slides" and "modify content", which maps to addSlides but not precisely.

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 names a specific action and resource: "Edit an existing PowerPoint (PPTX)", which clearly distinguishes it from create_pptx. However, "modify content" is vague and slightly overstates the schema, which only supports adding slides.

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 word "existing" implies this tool is for files that already exist, giving some contextual guidance. But there is no explicit statement of when to use this tool versus create_pptx or alternatives, and no exclusions are mentioned.

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