list_images

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

There are no annotations, so the description carries the behavioral burden. It scopes the operation to the current session, which is useful, and 'list' implies a read-only action. However, it does not disclose ordering, whether results include metadata or just identifiers, or any session-related constraints. For a simple list tool this is acceptable but not richly 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?

A single, front-loaded sentence with no filler. Every word contributes to the meaning, and the scope is stated immediately in the core clause.

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 operation with an output schema present, the description is nearly complete. It conveys the key scoping detail (current session) and relies on the output schema to define return values, which is appropriate. It is missing only minor behavioral nuance like ordering or result format, but nothing that blocks correct invocation.

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?

There are no parameters and the schema is empty, so the description needs to add little. The phrase 'current session' gives useful context about the implicit scope of the operation, satisfying the baseline for a zero-parameter tool.

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?

Clear verb-resource pair: 'list' + 'all images'. The scope 'in the current session' distinguishes it from per-image retrieval tools like get_image and mutation tools like delete_image. The simple name plus description leaves no ambiguity about what the tool does.

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 implies when to use it—when a full enumeration of the current session's images is needed—but it does not explicitly mention alternatives or state when not to use it. For a zero-parameter tool the inference is straightforward, but the guidance remains implicit rather than stated.

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