create_omni_voice

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool creates a reusable voice character and returns a kieAudioId, but fails to explain mutation implications, authorization needs, rate limits, or any side effects. The description is too brief to be fully transparent.

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 extremely concise: two sentences covering purpose, newness, use case, and output. Every sentence adds value with no wasted words. Front-loaded with 'NEW' and the core action.

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 moderate complexity of creating a voice character, the description covers the essential purpose and output linkage. However, it omits details on customization behavior and validation beyond what the schema provides. Still, it is largely complete for a well-schematized 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 schema already documents each parameter. The description adds no new parameter-level meaning beyond the schema. Baseline 3 is appropriate as the description does not need to compensate for coverage gaps.

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 verb (create), resource (reusable voice character), and context (Gemini Omni video generation). It also specifies the return value linking to generate_video. However, it does not explicitly differentiate from sibling tools like create_voice_clone, which creates a different type of voice resource.

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 a specific use case (video generation) and links to generate_video, but does not provide explicit guidance on when to use this tool versus alternatives such as create_voice_clone or prepare_voice_clone. No when-not or exclusion criteria are given.

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