Renforge Capture Screenshot

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the write target ('controlled capture directory'), which is genuinely useful, but it says nothing about overwrite behavior for the default 'capture' name, permissions, or what source is captured — significant gaps for a persist/write operation.

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 front-loaded sentence with no filler, which is structurally sound, but its brevity is under-specification rather than discipline given the tool's 13-parameter surface. Nothing beyond the destination directory is conveyed.

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?

An output schema exists, so return values need not be described, but for a 13-parameter snapshot tool with zero schema coverage and no annotations the description is far too thin. The capture source, cropping semantics, and overlay flags all go unexplained.

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% and the description mentions no parameters at all, leaving all 13 parameters (crop_x/y/width/height, crosshair_x/y, grid, scale, rulers, name, width/height) entirely undocumented. With this many non-obvious numeric and boolean controls, the description should compensate but does not.

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 gives a specific verb ('persist') and resource ('screenshot') plus a scope qualifier ('under the project's controlled capture directory'), so the operation and its destination are unambiguous. It does not, however, distinguish this from the sibling tool 'renforge_screenshot', which an agent must choose between.

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 guidance on when to use this tool rather than the similarly named 'renforge_screenshot', nor any stated prerequisites (e.g. a running game or an active window to capture). The agent must infer the selection criteria entirely from the name.

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