take_screenshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one genuinely useful trait — the native bridge expects `filepath` and the public `filename` is kept for compatibility and forwarded — but it never discloses where the screenshot is written, what side effects occur, or whether a running editor session is required.

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?

The description is compact and front-loaded, stating the purpose first, followed by the bridge nuance, a KB pointer, and a concrete call example. It is efficient, though the KB reference is terse and the example adds no parameter variety.

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 are covered, but the description otherwise leaves notable gaps: two of three parameters are undocumented across both schema and description, there is no differentiation from the overlapping sibling `viewport_capture_screenshot`, and no prerequisites are stated. For a tool with zero annotations and 0% schema coverage, this is insufficient.

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 for the schema's silence. It adds meaning only to `filename` via the filepath-forwarding explanation; `show_ui` and `resolution` remain completely unexplained in both the schema and the description, leaving two of three parameters opaque to the agent.

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 opening sentence states a specific verb and resource: 'Take a screenshot of the Unreal Editor viewport.' This is clear and unambiguous. However, it does not distinguish itself from the near-identical sibling `viewport_capture_screenshot`, so it misses the differentiation that would earn a 5.

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?

No guidance is given on when to use this tool versus alternatives such as `viewport_capture_screenshot` or `renderer_capture_viewmode`. The bridge note about `filepath`/`filename` is an implementation detail, not usage guidance, and there are no exclusions or preconditions stated.

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