get_image

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

The description discloses that the tool returns the actual image to the model, implying a read-only retrieval. Since no annotations are provided, the description carries the full burden for behavioral disclosure. While adequate for the core behavior, it omits potential side effects (e.g., does it consume the image? is there caching?) and does not address authentication or rate limits.

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 two paragraphs with some repetition (e.g., 'loop step 3: LOOK — part 2' revisited). It could be more concise by merging the first sentence and the loop context. Overall, it is somewhat verbose for the information conveyed.

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 three parameters with no schema descriptions and no output schema, the description leaves significant gaps: it does not explain which parameter is required (filename), what format identifiers take, or what the response contains. For a tool that returns binary image data, the absence of error handling or type hints is a deficiency.

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?

The description provides zero information about the three parameters (filename, subfolder, image_type). With 0% schema description coverage, the description must compensate but fails entirely. The agent receives no guidance on how to specify which image to fetch, making correct invocation difficult.

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 tool fetches a rendered output image for visual inspection, using active verbs like 'Fetch' and 'LOOK'. It distinguishes itself from siblings by embedding the tool in a loop workflow (step 3: LOOK), though it does not explicitly compare with similar tools like 'compare_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 explicit usage context: this is part of a loop where the agent should view pixels and judge against the brief before re-running. It advises against declaring workflow done based on a green run alone. However, it lacks explicit when-not-to-use or mention of alternatives like 'compare_images' for comparison tasks.

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