gemini_chat

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

The description adds behavioral context beyond annotations: it states that the output includes the model's reasoning process when using flash-thinking model. Annotations already indicate readOnlyHint=true and destructiveHint=false, so no contradiction. The description is transparent about the tool's behavior.

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 concise and well-structured: a single paragraph with 'Args' and 'Returns' sections. Every sentence adds value, and the main action is front-loaded. No unnecessary information.

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?

Given the tool's complexity (3 parameters, output schema exists, annotations present), the description is complete. It covers parameter semantics, return value, and special behavior (thinking model reasoning), providing all necessary context for an agent to use the tool correctly.

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?

With 0% schema description coverage, the description fully explains all three parameters: prompt (text to send), model (with examples and default), and session_id (for multi-turn context from gemini_start_chat). This adds significant meaning beyond the schema's basic titles and types.

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 purpose: 'Send a text prompt to Google Gemini and get a response.' It specifies the verb (send), resource (text prompt to Gemini), and outcome (get response). It also distinguishes from sibling tools like gemini_start_chat by mentioning session_id for multi-turn conversation.

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 provides some usage guidance, such as using the optional session_id from gemini_start_chat for multi-turn conversation and listing model options. However, it could be more explicit about when to use this tool compared to alternatives like gemini_analyze_url. The guidelines are mostly clear but not exhaustive.

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