get_image

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

There are no annotations, so the description carries the full burden. It mentions working with remote instances and not requiring COMFYUI_PATH. But it does not disclose error behavior (e.g., file not found), authentication needs, or rate limits. This is adequate but not thorough.

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 concise sentences with no fluff. Every sentence adds value: the first states the action and output, the second provides usage context and dependency information.

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?

No output schema, so description should clarify the return format. It says 'return it as an inline image' but does not specify the encoding (e.g., base64) or structure. It also lacks differentiation from sibling tools like 'view_image', given the large sibling list.

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 coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema, only referencing the 'filename' parameter indirectly. It does not explain the other parameters or their nuances.

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 it fetches a generated image from ComfyUI and returns it inline. The verb 'Fetch' and resource 'generated image' are specific. However, it does not explicitly distinguish from sibling tools like 'view_image' or 'list_output_images'.

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 a key dependency: 'Use get_history first to obtain the filename.' This helps the agent understand the workflow. However, it does not discuss when not to use this tool or alternatives.

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