Renforge Screenshot

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

With no annotations, the description carries the full burden. It does disclose real behavior — aspect-ratio preservation when only one of width/height is supplied, and the semantics of grid/rulers/crosshair overlays — but says nothing about the return format (image bytes? path?), whether the capture has side effects, or any permissions/state requirements.

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?

Front-loads the core action in one sentence, then adds implementation detail on the measurement overlays. It is appropriately sized and every sentence contributes; no 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?

For a 12-parameter tool with 0% schema coverage and no output schema, the description leaves notable gaps: crop and scale semantics, the meaning of project_path, and what the tool returns. It adequately covers the distinctive overlay features but not the whole calling surface.

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% across 12 parameters, so the description must compensate. It meaningfully explains grid, rulers, crosshair_x/crosshair_y, and the width/height aspect-ratio rule, but crop_x/crop_y/crop_width/crop_height and scale are only implied by 'cropping'/'resizing', and project_path (the sole required param) is never described. Roughly half the surface is covered.

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 names a specific verb and resource ('Capture a game frame') and enumerates the optional transformations (resizing, cropping, zooming), so an agent knows exactly what the tool produces. It stops short of distinguishing itself from the closely-named sibling 'renforge_capture_screenshot', leaving overlap unresolved.

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?

There is no explicit when-to-use guidance and no routing to alternatives, even though 'renforge_capture_screenshot', 'renforge_find_image_on_screen', and 'renforge_inspect_image' clearly overlap in scope. The measurement-guide sentence implies a use case for pixel-perfect placement, but it never frames this as a decision criterion versus siblings.

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