Add Image to PowerPoint

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

Annotations indicate destructiveHint=true, but the description does not explain the destructive behavior (e.g., file overwrite). It lacks details on prerequisites (image must exist), side effects, or response format. The description adds minimal behavioral context beyond the annotations.

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 concise with a front-loaded purpose, then bulleted params, then examples. No redundant sentences. The structure is logical and easy to scan, though the Args section could be slightly more compact.

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 nested objects and no output schema, the description covers basic functionality and parameters but omits important context such as file overwrite behavior, error handling, and return value. It is adequate but not comprehensive.

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 50% (borderline low), but the description essentially repeats the schema without adding extra meaning. It does not clarify units for x,y,w,h (already in schema) or provide nuances like coordinate origins. The examples are about usage, not parameter specifics.

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 'Create a new PowerPoint (.pptx) with one slide containing an image,' which is a specific verb-resource combination. It distinguishes from siblings like office_create_powerpoint (blank) and office_ppt_add_chart (chart). The 'Not for' note further clarifies scope.

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?

Examples like 'Use when: Create a slide with the company logo' and 'Not for: Creating slides without images' provide clear usage context. However, it does not explicitly mention alternatives like office_create_powerpoint for blank presentations, which could improve sibling differentiation.

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