title_render_compare

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

No annotations are provided, so the description must carry the behavioral burden. It states the core behavior (compare images and report pixel error) and the optional full-image vs. region scope. However, it does not disclose output format, units, error conditions, or prerequisites, leaving notable behavioral details unspecified.

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, front-loaded sentence that efficiently communicates the action, inputs, and output scope. Every word contributes meaning, with no fluff or repetition.

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?

With no annotations and no output schema, the description should clarify the return value, but it only says 'report pixel error' without specifying format, magnitude, or structure. It also does not mention any prerequisites or assumptions about image formats or paths. This leaves the tool under-specified for an agent to fully anticipate the result.

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 covers reference_path and render_path with short descriptions, giving 67% coverage. The description mentions the 'full image or region' capability, which hints at the region parameter's optionality but does not explain its format (e.g., order or meaning of the four integers). Thus the description adds minimal semantic value beyond the schema for the region parameter.

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 uses a specific verb ('Compare') and clearly identifies the resources (UE-rendered title frame vs. reference still) and the output (pixel error). It also distinguishes this from siblings like title_manifest_validate, which is about manifest validation rather than visual 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 implies when to use the tool (when a rendered title frame needs to be compared to a reference still) but does not explicitly state alternatives or exclusions. No sibling tool appears to perform a similar pixel comparison, so there is no direct alternative named, leaving the usage context implicit.

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