List Google Ai Chats

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

With no annotations, the description carries the full behavioral burden. "Locally stored" usefully discloses that results come from a local store rather than a live service, implying prior import/sync, but it says nothing about pagination defaults, ordering, empty-result behavior, or result size limits for a 3-parameter listing tool.

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?

One short sentence that front-loads the verb and resource with the scope qualifier immediately after. Nothing is wasted, though the extreme brevity leaves gaps that a second sentence could have cheaply filled.

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?

An output schema exists, so return values needn't be explained, and the tool is conceptually simple. Still, for a paginated list tool with zero-documented parameters and no annotations, the definition leaves the agent guessing about page size behavior and how to narrow by source.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does not. The enumerated sources (Gemini, Search AI Mode, AI Studio, Ask Maps) loosely suggest what the `source` filter accepts, but it never maps them to that parameter or gives exact string values, and `limit`/`offset` are entirely unexplained.

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?

States a specific verb and resource ("List ... Google AI chats") and adds qualifying scope with "locally stored" plus a concrete enumeration of sources (Gemini, Search AI Mode, AI Studio, Ask Maps). This is enough to distinguish it from the more investigative sibling search_google_ai_chats, though it never names the sibling explicitly.

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 word "List" plus "locally stored" implies a browse-all operation rather than a query, which hints at when to prefer it over search_google_ai_chats or get_google_ai_chat. However, there is no explicit when-to-use/when-not statement, no mention of prerequisites such as importing or syncing data first, and no routing to any of the five siblings.

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