list_models

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

With no annotations, the description only states that it lists IDs, without disclosing any behavioral details such as whether the list is comprehensive, sorted, or if it might return empty. The description is straightforward but does not go beyond the obvious.

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, focused sentence with no redundant wording. It front-loads the action and resource.

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 simple, no-parameter listing tool, the description adequately conveys its purpose and relationship to sibling tools. Although no output schema exists, the phrase 'List ... ids' sufficiently indicates the return type is a collection of model IDs.

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 zero parameters, so the schema already covers all inputs. The description adds no parameter semantics, but none are needed. Per the baseline for 0-param tools, this scores 4.

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 uses a specific verb 'List' and clearly specifies the resource as 'Gemini image model ids' and its purpose 'usable with generate_image/edit_image'. This distinguishes it from its siblings which perform generation/editing.

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 it is used to obtain model ids for generate_image and edit_image, but does not explicitly state when to call it or when not to. It provides clear context but lacks explicit alternative guidance or exclusions.

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