ppt_visual_diff

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

With no annotations, the description carries the full burden. It discloses the 'deterministic' nature and what outputs are generated, which is useful. However, it does not clarify whether files are written to disk (output_diff_path implies that), any side effects, or prerequisites like rendering the slide first.

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 a single sentence that is concise and well-structured, front-loading the core action and outputs without any filler.

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?

This is a moderate-complexity tool with an output schema present. The description gives the core purpose and outputs, which is adequate for basic understanding, but it misses important usage context (when to use, parameter semantics, potential side effects). Given no annotations, more detail would be needed to make it fully complete.

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 0%, and the description must compensate. It indirectly references the two images ('two slide renders'), but does not explain the threshold parameter or output_diff_path. With four parameters and no other descriptions, this is a significant gap for an agent to use the tool correctly.

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 tool performs pixel-level image comparison between two slide renders, listing specific outputs (diff image, bounding boxes, similarity metrics). This is a specific verb+resource and distinguishes it from the sibling ppt_compare_slides which likely does a different type of comparison.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that this is for visual diffing rather than structural comparison, nor does it reference ppt_compare_slides or any context for choosing it.

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