gimp_render_compare

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

With no annotations, the description carries the full behavioral burden. It explains that 'diff = pixel difference, black means identical,' which is useful, but it does not disclose the effect of drop_snapshot, whether the snapshot is deleted, the output format, or any side effects. For a tool with a boolean drop_snapshot parameter, this is a significant gap.

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?

Two sentences with no filler. The first sentence front-loads the core purpose, and the second explains the key parameter. Every part earns its place.

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?

Given five parameters, no output schema, and no annotations, the description is not complete enough. It omits the meaning of drop_snapshot and max_size, does not describe the return value, and does not mention whether the snapshot persists after the operation. An agent would be guessing on important invocation details.

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 0%, so the description must compensate. It adds meaning only for panels ('comma list of before, after, diff'), leaving image_id, snapshot_id, max_size, and especially drop_snapshot without clarifying semantics. Property names alone are not enough for unambiguous invocation.

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 and resource: 'Side-by-side render of a snapshot and the current image.' This clearly distinguishes the tool from siblings like gimp_render or gimp_snapshot, and the follow-up sentence about panels adds concrete 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?

The purpose implies when to use it: when a comparison between a snapshot and the current image is needed. However, it does not explicitly name alternatives or state when not to use it, leaving the routing decision to inference rather than direct guidance.

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