Gemini List Image Sessions Tool

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

No annotations provided, so the description carries the full burden. It says 'active' sessions, which is useful, but says nothing about session lifetimes, what happens to ended sessions, result format, scoping (user/workspace), or rate limits. For a list tool with zero annotations this is thin.

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?

Single, front-loaded sentence with no waste. Appropriate length for a zero-param list tool, though it could condense into a slightly richer sentence without bloat.

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?

Output schema exists so return value explanation is not needed, and there are no parameters to document. However, with no annotations and many sibling session tools, the description should clarify scope and relationship to start/continue/end session tools. Adequate but with a clear gap.

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?

Zero parameters, so baseline is 4. The description correctly implies no inputs are needed and the empty schema is consistent; no additional semantics required.

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?

Specific verb 'List' plus resource 'active image editing sessions', which is clear. But it does not differentiate from siblings like gemini_list_caches_tool or explain what a session is versus continue/end/edit tools. Still relatively unambiguous for a zero-param list 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 indication of when to use this versus gemini_start_image_edit_tool or gemini_continue_image_edit_tool. Sibling routes exist but the description offers no routing guidance. Implied usage at best.

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