ui_screenshot

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

No annotations exist, so description is critical. It mentions returning a file path and reading with image tooling but lacks details on capture scope, permissions, or behavior with the 'path' and 'window_only' parameters. Minimal disclosure.

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 sentences with no extraneous text. First sentence states purpose, second sentence provides usage guidance. Perfectly concise and front-loaded.

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?

With no output schema and minimal description, the tool lacks completeness. Parameters are unexplained, and the return value is only vaguely described as a file path. For a tool of this complexity, more detail is needed.

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 provides no explanation of the two parameters ('path', 'window_only'). Users must infer their meaning from names alone, which is insufficient.

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 tool captures Resolve's window to a PNG for state inspection. It distinguishes itself from siblings with a unique action (screenshot) not replicated elsewhere.

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 description suggests using the screenshot to check UI action results before proceeding. While it doesn't list when-not-to-use or alternatives, the context is clear and implies a specific workflow.

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