Add Table Slide to PowerPoint

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

Annotations indicate destructive write operation, and description confirms creating a new file. Add context that it creates exactly one slide with a table, no contradiction, but could mention overwrite behavior explicitly.

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?

Concise two-line summary followed by well-organized Args list and examples, front-loaded and no waste.

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?

Covers purpose, usage, and parameters well, but lacks description of return value/output. Since no output schema exists, description could add what the tool returns (e.g., file path or success status).

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?

Description documents filePath, table headers, rows, and a subset of options (fontSize, fontFace, borderColor, colW) but omits x, y, w, borderSize, rowH from the schema, giving partial coverage.

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 it creates a new PowerPoint file with a single slide containing a formatted table, using specific verb 'Create' and resource 'PowerPoint .pptx', distinguishing it from sibling tools like office_ppt_add_chart.

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?

Provides explicit 'Use when' examples and a 'Not for' case with an alternative tool (office_create_powerpoint), giving clear guidance on when to use this tool vs alternatives.

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