ue_screenshot

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

No annotations are provided, so the description carries the full burden. It discloses that the file is saved to <Progetto>/Screenshots/MCP, that the default resolution is modest to avoid large base64 responses, and that return_image=False only returns the path. These details go beyond the bare minimum.

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 front-loaded with the core purpose and includes a rationale, storage info, resolution advice, and parameter documentation. It is slightly verbose but every sentence adds value; no waste.

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?

For a simple screenshot tool with 4 parameters, the description covers all necessary aspects: what it does, why it's needed, file persistence, resolution considerations, and parameter details. No output schema exists, but the tool's return type (image or path) is adequately described.

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?

With 0% schema description coverage, the description fully documents all 4 parameters: filename, width, height, and return_image. It explains default behaviors (timestamp, resolution trade-offs) and the effect of return_image, adding significant meaning beyond the schema types.

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 'Cattura la viewport dell editor e restituisce l immagine all agente', which translates to capturing the editor viewport and returning the image. This verb+resource combination is specific and distinct from sibling tools like ue_set_camera or ue_render_sequence.

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 explains that without this tool the agent builds blindly and it is the only way to verify the scene visually, providing clear context for when to use it. It also warns about resolution trade-offs but does not explicitly mention alternatives or when not to use it.

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