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 a valuable side effect — the image is written to disk and a path returned ('plus its saved path') — but omits where files are saved, naming/overwrite behavior, and whether capture requires the window to be visible or active.

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 tight sentences with the capability first and the return value second; no filler, nothing buried.

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?

No output schema exists, and the description does cover the return value (PNG plus path), which is a plus. But for a three-parameter, zero-annotation tool with 0% schema coverage, the missing parameter-to-mode mapping and disk-write details leave real gaps.

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 hints at 'window' and 'object_name' through the target list, but leaves 'name' (presumably the output filename) completely unexplained and never states which arguments are mutually exclusive or combinable.

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 ('Capture') and names three concrete targets (QGIS main window, a window, one widget), plus what it returns. It is clearly distinguishable from siblings like list_windows or dump_widgets, though it never maps the three targets to the three parameter names.

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 guidance on when to use this tool, which parameter combination selects which capture mode, or what the defaults do when all three arguments are omitted (all are optional). The three targets are listed but not tied to any selection rule, so the agent must guess.

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