run_comparison_manifest

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

With no annotations, the description carries the behavioral disclosure burden, but it only hints at persistence via 'preserve aggregate results.' It does not disclose side effects, required setup, whether results are overwritten, authentication needs, or how output is accessed.

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?

A single sentence with no filler; every phrase ('Run', 'saved', 'image-comparison manifest', 'preserve aggregate results') contributes meaning and the core action is front-loaded.

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 no output schema and no annotations, the description is too thin: it omits how results are preserved or returned, what the manifest string should contain, and how this differs from compare_renders. An agent could not reliably invoke it correctly from this description alone.

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?

The schema only gives a string named 'manifest' with 0% description coverage. The description adds the minimal context that the manifest is saved and image-comparison related, but it does not specify whether the value is a path, ID, name, or inline content, leaving the agent without enough to populate the parameter 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 states a specific action ('Run') on a specific resource ('a saved image-comparison manifest') and adds the outcome of preserving aggregate results. The phrase 'saved manifest' differentiates this from direct comparison tools like compare_renders.

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 wording implies the tool is for executing previously saved comparison manifests, but it does not explicitly state when to choose it over sibling alternatives or list exclusions. No when-not-to-use guidance is provided.

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