pptx_add_slide

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but description adds value by disclosing that output_path defaults to overwriting input, which is a key behavioral detail. It does not mention other side effects like file locking or error conditions, but covers the main mutation behavior.

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 well-structured with sections and bullet points for layout values. However, the layout list is somewhat lengthy; could be more concise while retaining clarity. Still front-loaded with the primary purpose.

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 5 parameters (1 required), no output schema, and sibling tools, the description covers all parameters with defaults and examples. It also mentions using pptx_list_masters for more layouts. The return value 'Status with new slide_number' is sufficient for context.

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?

With 100% schema coverage, baseline is 3. The description adds meaning beyond schema: for layout_index it lists common values (0,1,5,6) with descriptions, for position it gives examples, and for output_path it states the default overwrite behavior. This enhances parameter understanding.

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 'Add a new slide to an existing presentation,' specifying the action and resource. It distinguishes from siblings like pptx_duplicate_slide or pptx_delete_slide by focusing on slide addition.

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 provides common layout_index values and position options, aiding selection, but lacks explicit guidance on when to use this tool versus alternatives like pptx_duplicate_slide or pptx_import_slide. No 'when to use' or 'when not to use' statements.

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