gemini_dialogue_tool

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

With no annotations, the description carries the full burden, but it only restates the action. It does not disclose output format, whether the audio is returned as a file/URL, how speaker labels map to voices, or any other behavioral traits.

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, focused sentence that immediately communicates the purpose without redundancy. It is front-loaded and appropriately concise.

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?

Despite having parameter descriptions and an output schema, the description is under-specified. It lacks guidance on how to format dialogue text, how the two voices are assigned to speakers, and when to use this tool over gemini_speak_tool, making it incomplete for a generation tool.

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 baseline is 3. The description adds no additional meaning beyond the schema; it does not clarify how 'text' with speaker labels should be structured or how voice1/voice2 are used.

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 'Generate multi-voice dialogue audio' clearly states the tool's function with a specific verb and resource. The 'multi-voice dialogue' qualifier differentiates it from sibling tools like gemini_speak_tool (single-voice speech) and gemini_generate_video_tool.

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 usage guidance is provided. The description does not mention when to use this tool vs alternatives, nor does it note any exclusions or prerequisites. It only defines the core action.

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