continue_google_ai_session

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

With no annotations, the description must fully disclose behavioral traits. It mentions returning updated conversation and defaulting to active session, but omits key details: it modifies session state, may consume API quota, and likely requires prior session creation. No mention of side effects, error conditions, or required permissions.

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, well-structured sentence that conveys the essential information without extra words. It is front-loaded with the core 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?

While the tool is simple and the schema covers parameters, the description misses behavioral context such as error handling, side effects (e.g., modifying session state), and return format details. Without an output schema, the description should clarify what 'updated visible conversation' entails, but it does not.

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 4 parameters. The description adds minimal extra value: 'Defaults to the active session' for sessionId is redundant with the schema. No additional meaning beyond schema is provided.

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 ('Send a follow-up message'), the resource ('persisted Google AI conversation session'), and the return value ('updated visible conversation'). It distinctly differentiates from sibling tools like 'start_google_ai_session' and 'end_google_ai_session'.

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 usage after starting a session with 'Defaults to the active session', providing clear context. However, it lacks explicit exclusions or when-not-to-use guidance, and does not mention alternatives like 'google_ai_ask' for non-persistent conversations.

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