Desktop Screenshot

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

No annotations are supplied, so the description carries the full behavioral burden and does little with it. It does not disclose the image format, whether an existing file at output_path is overwritten, whether parent directories are created, or what happens when the named app has no visible window — all material for a tool that writes to disk.

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, and the action order (capture then save) is clear. It is arguably too terse given the undocumented parameters, but nothing in it is wasted.

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 explained, but the definition leaves an unannotated write-capable tool with 0% schema coverage and two ambiguous required parameters. For a desktop-automation capture tool, the description should at minimum clarify app identification and overwrite behavior.

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 both parameters are bare strings, so the description is the only source of meaning. 'Application window' and 'target path' only loosely gloss the names; it never says whether 'app' is a process name, bundle identifier, or window title, nor what path format is expected.

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 verb+resource pair ('take a screenshot of an application window') plus a persistence action ('save to target path'), so the agent knows exactly what the tool produces. It does not, however, distinguish itself from the sibling desktop_snapshot, which is likely the competing capture tool.

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 prefer this over desktop_snapshot, desktop_status, or desktop_list_windows, and no prerequisites such as the window needing to be visible or the app running. The agent must infer the selection rule entirely.

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