renforge_inspect_image

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently indicates a read-only operation ('Open' and 'return') and describes the main transformation (cropping/zooming), but it does not explain what happens with default values, invalid paths, or whether the original file is ever modified.

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, tightly worded sentence that is front-loaded with the key action. It is concise and free of filler, though the brevity comes at the cost of omitting necessary detail.

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 6 parameters, no annotations, no output schema, and zero parameter description coverage, this description is not complete enough for reliable invocation. It lacks guidance on coordinate systems, default behavior, output format specifics, and error handling.

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 by explaining the 6 parameters. It only hints at 'cropped/zoomed' behavior, but never explains scale units, crop coordinate origin, or how zero values for crop dimensions are interpreted. Agents would need to guess or infer parameter semantics.

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 action ('Open'), the resource ('a local image'), and the output ('an optional cropped/zoomed PNG for inspection'). This differentiates it from sibling tools like renforge_inspect_screen or renforge_screenshot, which deal with the live screen rather than local image files.

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 phrase 'for inspection' gives a clear intended use case, and 'local image' provides context that distinguishes it from screen-oriented tools. However, it does not explicitly mention when not to use this tool or name alternative tools for related tasks.

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