view_image

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

With no annotations provided, the description must fully disclose behavioral traits, including side effects (e.g., opening a viewer window), prerequisites (e.g., a rendered image must exist), or limitations (e.g., image format support). The description only mentions loading an image but omits these details, leaving the agent unaware of important behavioral context.

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 very short, with a clear main sentence and a structured Args section for the parameter. It is efficient and front-loaded, but could be slightly more informative without adding length (e.g., mentioning file type support). The conciseness is commendable, but it leans toward under-specification.

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?

Given the tool's simplicity (1 param, no output schema), the description covers the basic action but omits context about what 'load a rendered image' entails (e.g., does it open a GUI window or return the image data?). Without annotations or output schema, the description should provide more behavioral completeness, which it fails to do.

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 should compensate by explaining the 'path' parameter. The description notes 'relative to the output folder unless absolute', which adds some meaning, but it does not clarify expected formats (e.g., file extension) or relationship to other tools' outputs. This is marginally helpful but insufficient for a single parameter with no schema documentation.

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 'Load a rendered image so it can actually be looked at', which gives a specific verb ('load') and resource ('rendered image'). However, it lacks differentiation from siblings like 'view_reference' or 'view_preview', which may serve similar purposes. The purpose is clear but not distinct.

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 provides no guidance on when to use this tool versus alternatives like 'view_reference' or 'view_preview'. There are no exclusions or context for when this tool is appropriate, which is a significant gap given the presence of multiple similar tools in the sibling list.

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