get_image

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

With no annotations, the description tells that it returns an inline image and works remotely, but lacks details on response format, side effects (none?), or error handling. Adequate but could be more transparent.

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, no fluff, front-loaded with the core action. Every sentence provides necessary information efficiently.

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 fetch tool with no output schema, the description covers the main aspects: action, prerequisite, and remote compatibility. Missing explicit return type, but overall complete enough.

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 covers all 4 parameters with 100% coverage. Description adds value by explaining the filename comes from get_history and the default save_dir behavior, going beyond the schema.

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 action ('Fetch a generated image from ComfyUI'), the resource ('inline image'), and distinguishes from siblings by noting it works with remote instances and does not require COMFYUI_PATH.

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?

Explicitly recommends using get_history first to obtain the filename, and clarifies the tool works remotely. Does not mention alternatives or when not to use, but provides sufficient context for appropriate use.

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