create_character

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

The description mentions the return values (task id, status, output URLs) but does not disclose the async nature, polling behavior, or any side effects. With no annotations, the description carries full burden but provides minimal behavioral context.

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, concise sentence with no wasted words. It front-loads the purpose and return values, making it easy to scan.

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 has 6 parameters, async behavior (implied by wait/polling params), and no output schema, the description is woefully incomplete. It does not explain how to use the tool effectively or what the output shape is.

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 coverage is only 33%, meaning most parameters lack descriptions. The description does not explain critical parameters like 'descriptions' or 'reference_image_url', nor does it add meaning beyond the schema. With low coverage, the description fails to compensate.

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 it creates a Gemini Omni task specifically for a character, with a verb and resource. However, it does not differentiate from sibling tools like create_audio or text_to_video, which also create tasks.

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 guidance on when to use this tool versus alternatives such as create_audio or text_to_video. The description lacks any context about prerequisites or use cases.

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