gemini_list_image_sessions_tool

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states 'List' but doesn't explicitly confirm this is a read-only operation, how 'active' is defined (e.g., not yet ended, currently running, not expired), or whether listing has any side effects. The description adds no behavioral context beyond the literal action.

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, front-loaded sentence with no fluff. Every word contributes to meaning and it is appropriately concise for such a simple tool.

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 tool with an output schema, the description is minimal but not fully complete. It leaves 'active' undefined and doesn't explain how sessions are scoped or whether they are cleared after listing. The output schema likely covers return structure, but the lack of context around session lifecycle and usage flow makes this merely adequate.

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 accepts zero parameters, so the input schema is already complete. The description has no parameter details to add, and the baseline for zero-parameter tools is 4. No additional explanation is needed.

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's function: 'List all active image editing sessions.' It uses a specific verb (list) with a distinct resource (image editing sessions) and a qualifier ('active'). This distinguishes it from sibling tools like gemini_start_image_edit_tool and gemini_list_voices_tool.

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?

No guidance is provided about when to use this tool versus alternatives. It doesn't mention that it could be used to retrieve session IDs before continuing or ending edits, or any workflow context. The description simply states the action without any clues about prerequisites or typical use cases.

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