list_images

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

With no annotations, the description must carry behavioral disclosure. It does reveal what output fields will be present, which is useful, and the 'every image datablock' phrasing implies a read-only enumeration. However, it does not explicitly state that this is non-destructive, how results are structured, or whether packed/external images are handled differently.

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 a single concise sentence that communicates the resource and the data fields without wasted words. It is front-loaded and easy to parse.

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 zero-parameter list tool with no output schema, the description covers the core need: the tool returns every image datablock with the specified attributes. The term 'usage' is slightly vague, and there is no explicit statement of the return shape, but the definition is otherwise sufficient for a simple listing operation.

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 tool has zero parameters, so the description does not need to explain parameter syntax or semantics. The baseline of 4 applies because the schema is empty and there is nothing else required from the description.

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 identifies the resource ('image datablock') and the relevant fields (path, resolution, colour space, usage), making it clear this is an enumeration of all image datablocks. However, it lacks an explicit verb like 'list' or 'returns', and it does not distinguish itself from sibling tools like get_image or load_image.

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 gives no guidance on when to use list_images versus alternatives such as get_image, create_image, or load_image. There is no mention of exclusions, prerequisites, or the appropriate context for requesting all images.

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