gemini_chat

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions multi-turn conversations and image limits (max 10), which are useful, but lacks critical details like rate limits, authentication needs, response format, or error handling. This is inadequate for a chat tool with potential complexity.

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, efficient sentence that front-loads the core purpose and key features (multi-turn, image support). Every word earns its place with no redundancy or fluff.

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 chat tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on response format, error cases, rate limits, and how it integrates with siblings like clear_conversation or get_image_history. More context is needed for effective use.

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 100%, so the schema already documents all parameters thoroughly. The description adds no additional meaning about parameters beyond implying image support aligns with the 'images' parameter. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Chat with') and target ('Gemini 3.1 Flash model'), and mentions multi-turn conversations and image support. However, it doesn't explicitly differentiate from siblings like gemini_edit_image or gemini_generate_image, which also interact with Gemini but for different purposes.

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 mentions multi-turn conversations and image support, which implies usage for interactive chat with visual inputs. However, it provides no explicit guidance on when to use this tool versus alternatives like gemini_edit_image or set_model, nor does it mention prerequisites or exclusions.

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