Chat with Gemini

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

Annotations already declare non-readOnly, openWorld, non-idempotent, non-destructive, so the description earns credit for adding that the call blocks until generation finishes and returns text, plus the thinking-level behavior. It stops short of disclosing that the chat is stateful across calls (continuity only hinted at by new_chat) and says nothing about timeout/failure 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?

Three front-loaded sentences with the action first and the return contract last; nothing is padded. The inline enumeration of model aliases is slightly redundant with the schema enum and is the only wasteful element.

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 five-parameter, no-output-schema tool with full schema coverage, the description explains the action, the blocking wait, and the text return, which is enough to call it correctly. The main gap is conversational statefulness and what happens on timeout, which an agent would need to reason about.

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 documents all five parameters. The description's model aliases and thinking levels largely duplicate the enum values rather than adding new meaning (e.g., what 'Argon' maps to, or whether thinking_level applies to non-reasoning models).

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 ('Send a prompt to Gemini web') plus the return behavior ('returns the text'), so the core action is unambiguous. It doesn't differentiate from siblings like gemini_upload_and_ask or gemini_switch_model, even though it partially overlaps their functionality via the model parameter.

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 when-to-use or when-not-to-use guidance is given, and no sibling is named as an alternative. The description advertises model switching inline, which overlaps gemini_switch_model, but never says when to use this tool versus that one.

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